swagger-petstore---openapi-3.0.deleteOrder

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

The description aligns with annotations (destructiveHint=true, idempotentHint=true, readOnlyHint=false) and does not contradict them, but it adds no extra behavioral context beyond stating it deletes. The annotations already carry the safety profile, so the description's contribution is minimal.

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, concise sentence that front-loads the key information (delete order) and is free of fluff. It is efficient and easy to parse.

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?

Given the empty schema and lack of output schema details, the description is insufficient. It doesn't explain the required identifier, error scenarios (e.g., order not found), or side effects, and it doesn't provide enough context for an agent to confidently invoke the tool with correct parameters.

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, but the description hints at an identifier requirement ('by identifier') without specifying where or how it is provided (likely a path parameter). This is incomplete, and the description fails to compensate for the empty schema, leaving the agent to guess the identifier source.

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 the verb 'Delete' followed by the resource 'purchase order' and specifies 'by identifier', making the tool's purpose clear. It distinguishes from sibling delete tools (deletePet, deleteUser) by targeting orders, though it doesn't explicitly say 'order ID'.

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 given on when to use this tool versus alternatives like deletePet or deleteUser. The description only states what it does without providing context on prerequisites, error cases, or when not to use it.

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