delete_application

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond annotations: deletions are soft and moved to the trash, meaning the record can be restored later. That is meaningful disclosure for a mutation tool.

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 first two sentences are redundant ('Delete an application. Delete an application using its unique identifier.'). The recoverability detail at the end earns its place, but the opening restates the name rather than front-loading the unique soft-delete behavior.

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 single-parameter destructive tool with rich annotations and no output schema, the description is largely complete: it conveys the action, the identifier requirement, and the soft-delete/restore behavior. It leaves minor gaps around permissions and idempotency, but the annotations carry those.

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?

There is one nested parameter (path.applicationId) with a low schema description coverage. The description compensates partially by stating the identifier is unique to the application, but it does not clarify the nesting/path structure or the identifier format beyond what the schema implies.

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 a specific verb and resource ('Delete an application') and adds that a unique identifier is required, which is clear. It implies the soft-delete nature that distinguishes it from a hard delete, but never explicitly names the sibling restore_application, so sibling differentiation is only partial.

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?

There is no explicit guidance on when to use this tool versus restore_application, post_batch_delete_applications, or put_application. The note that deletions can be restored hints at reversibility but is not framed as usage guidance or prerequisites.

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