petstore-api.deleteOrder

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the destructive nature is disclosed. The description adds 'by identifier' but does not elaborate on irreversibility, required permissions, or the fact that no input schema parameters are declared. No contradiction with 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?

One short, front-loaded sentence with no unnecessary verbiage. It is instantly parsable and contains exactly the core information (action + resource + qualifier).

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?

While an output schema exists (so return format is covered), the tool's input contract is unclear because the schema is empty and the description does not explain how to supply the identifier. Annotations help with safety but not with calling conventions. Complete enough for a trivial delete but lacking required invocation details.

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 is empty, yet the description mentions 'by identifier', implying an input that is not formally declared. This creates ambiguity about how to pass the identifier. The description adds some meaning beyond the schema but fails to specify the parameter name, location, or format.

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 uses the specific verb 'Delete' and identifies the resource as 'purchase order' with a 'by identifier' qualifier. This clearly distinguishes it from sibling tools like getOrderById (retrieves) and deletePet (different resource).

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 description provides no guidance on when to use this tool, such as prerequisites (e.g., order must exist) or alternatives (e.g., use getOrderById to verify before deletion). It simply states the action without any context for selection among many sibling tools.

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