batch_update_issues

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

Discloses key behaviors: parallel execution, batch limit, replacement behavior for labels/assignees, and return format including success_rate and failed count. No annotations are present, so the description carries the full burden; it does so fairly well, though it could mention idempotency or error handling.

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?

Two concise paragraphs with no redundant information. The core purpose, update object format, replacement note, and return format are all front-loaded. 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?

Provides the output schema in the description, which helps. However, it does not cover prerequisites like issue existence, authentication, or the meaning of 'owner' and 'repo' parameters. Given the batch complexity and lack of annotations, it is minimally adequate but has gaps.

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?

0% schema coverage means the description must explain parameters. It details the 'updates' array structure but omits explanations for 'owner', 'repo', and 'max_workers' (only implied by 'parallel'). Most parameters lack semantic guidance.

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?

Clearly states the tool updates multiple GitHub issues in parallel with a max batch size. The verb 'update' and resource 'multiple GitHub issues' are specific and distinguish it from siblings like batch_add_labels which only add labels.

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?

No explicit guidance on when to use this tool versus alternatives like batch_add_labels for label-only updates. The description implies batch updates but does not provide when-to-use or when-not-to-use scenarios.

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