Bulk Execute

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

Annotations are minimal (no readOnly/destructive hints). Description adds 'Destructive tools are not allowed' (consistent with annotations) and explains parallelism and concurrency. This provides useful behavioral context beyond annotations.

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?

Three sentences, no redundant information. Front-loaded with the core purpose. Every sentence adds value.

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?

Description covers purpose, targeting, restrictions, and return format (per-router results with counts). No output schema, but description sufficiently describes what to expect. Minor gap: no mention of error handling or partial failures.

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?

Input schema has 100% coverage with descriptions, but description adds important context: targeting methods (routerIds or tags), restriction on destructive tools, and note that routerId is injected per router, not supplied. This enhances understanding beyond schema alone.

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?

Description clearly states 'Fan out a single-router tool to multiple routers in parallel' and mentions returning per-router results with counts. This uniquely differentiates it from all sibling tools, which are individual operations.

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?

Description specifies targeting via routerIds or tags and explicitly disallows destructive tools. While it does not provide explicit 'when to use' vs alternatives, the context implies it is for bulk operations not available elsewhere.

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