Delete Bulk Coordination Issues

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

Annotations indicate destructiveHint=true and readOnlyHint=false, but the description erroneously states 'Creates a new Coordination Issues...', directly contradicting annotations. No additional behavioral details such as irreversibility or permission requirements are provided.

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?

Repetition of the purpose ('delete a batch' / 'perform the delete bulk action') and inclusion of the erroneous creation sentence make the description bloated. While it provides the endpoint path, conciseness is compromised by redundancy and misinformation.

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?

Despite no output schema, the description fails to explain what the response contains, error handling, batch size limits, or idempotency behavior. Annotations cover destructiveness, but the description should complement them with more context about the operation's effects.

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 coverage is 100%, so the description adds minimal value. It lists required parameters and describes 'deletes' as 'an array of objects containing resource id to delete', which mirrors the schema description. No further clarification or constraints are provided.

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 description clearly states the tool is for deleting a batch of CoordinationIssues, using the verb 'delete' and specifying 'batch'. However, there is a confusing sentence about creating a new coordination issue, which is a copy-paste error and slightly undermines clarity.

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 guidance on when to use this tool versus alternatives like 'delete_coordination_issue' or 'create_and_update_bulk_coordination_issues'. The description only says 'use this to perform the delete bulk action' without context or exclusion criteria.

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