petstore-api.deleteUser

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description adds no new context. It does not explain irreversibility, authorization requirements, or side effects on related data, leaving the behavioral profile sparse beyond the 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?

The description is a single, front-loaded sentence that directly states the action and resource. No wasted words, perfectly concise.

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 delete tool with no parameters, the description fails to clarify which user is deleted or what the output schema represents. The existence of an output schema is not leveraged, and the ambiguity around the target user is a significant gap in functional completeness.

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?

The input schema has zero parameters, and schema description coverage is 100% vacuously. The description correctly does not need to explain parameters, and the baseline for 0 params is 4. However, it could have noted how the target user is determined (e.g., via auth context), but this is not strictly a parameter semantics issue.

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 operation ('Delete') and the resource ('user'), differentiating it from sibling tools like deletePet and deleteOrder. However, it lacks specificity about which user is targeted, especially since the input schema is empty.

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 is provided on when to use this tool versus alternatives. The description does not mention any prerequisites, context, or exclusions, and there are near-duplicate sibling tools (e.g., swagger-petstore---openapi-3.0.deleteUser) with no distinguishing information.

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