delete_applications_bulk

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description says 'Delete Application,' which is consistent with destructive. It adds the instruction to read the schema first, but no further behavioral disclosure beyond annotations. No contradiction.

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 very short (three lines), front-loads the purpose, and contains no filler. It is appropriately concise for the tool's simplicity, though minimal.

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 bulk delete operation, the description does not clarify that it deletes multiple applications (only states 'Delete Application' singular), and it relies entirely on the schema pointer for body fields. An output schema exists so return values are covered, but the description is thin on behavioral scope and prerequisites.

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 0% for the 'body' parameter, so the description must compensate. It says 'Request payload,' which merely restates the obvious, and directs to read the schema endpoint for fields, but does not provide actual parameter meaning or structure. This is insufficient given the lack of schema detail.

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 states 'Delete Application' and gives the endpoint /api/v1/applications/bulk, clearly identifying the resource and bulk operation. The name distinguishes it from delete_applications_by_id, though the description itself does not explicitly contrast the two scopes.

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 only usage hint is 'Read the matching GET or the /schema endpoint first to see the fields this resource expects,' which guides parameter preparation but does not explain when to choose this tool over delete_applications_by_id or other bulk operations. No explicit when/when-not guidance is provided.

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