cdp_batch

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says the tool 'runs' a command but does not mention side effects, safety risks, session requirements, or what happens on execution. For a raw CDP command execution tool, this is a significant transparency gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no filler, and the core instruction is front-loaded. It earns its place, though it is terse to the point of under-specification.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool that executes CDP bridge commands, the description is incomplete. It lacks usage context, behavioral caveats, and parameter detail. The output schema reduces the need to document return values, but the remaining gaps are material, especially with no annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It does clarify that batch_json is a full JSON command object passed as text, but it gives no structure or example, and it entirely ignores session_id. This is only minimal compensation for a required parameter with no other documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Run' and resource 'CDP bridge batch command' identify the basic action, and the word 'batch' loosely distinguishes it from the sibling cdp_command. However, 'CDP bridge batch command' is jargon and is not explained, so an agent cannot reliably infer what a batch command actually contains or how it differs from the single-command sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no guidance on when to use this tool versus cdp_command or any other sibling. The phrase 'CDP bridge batch command' vaguely implies a batch context, but there is no explicit when-to-use/when-not-to-use guidance or mention of alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.