petstore-api.deletePet

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, which describe the mutation. However, the description adds nothing beyond this—it does not clarify that the pet is identified by an ID, nor does it disclose potential failure modes (e.g., 404 if not found) or side effects. The empty input schema worsens the gap, as the agent is left unaware of how to specify which pet to delete. The description fails to add value beyond 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 short sentence, 'Deletes a pet.' It is front-loaded and contains zero wasted words. This is appropriately concise for a simple, atomic action. No structural issues.

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 low complexity, the description is still incomplete. It fails to explain how the pet is identified (no parameters in schema, no mention of an ID), what happens on success or failure, and how it differs from other delete operations. The output schema exists but does not compensate for the missing identifier guidance. The tool is too vague to be used confidently without additional information.

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, so schema coverage is trivially 100%, and the baseline for 0 params is 4. The description does not need to elaborate on parameters; however, it could have implied that the target pet is identified via some external context (e.g., path variable), but since none is given, the score remains at baseline.

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 action: 'Deletes a pet.' This uses a specific verb and resource, distinguishing it from sibling operations that add, update, get, or find pets. It is unambiguous and immediately conveys the tool's function.

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 versus alternatives like deleteOrder or deleteUser. There is no mention of prerequisites (e.g., the pet must exist), nor any clarification that this is for deleting a specific pet identified by ID. The context is implied by the name but not explicitly described, leaving room for confusion among the many sibling deletion tools.

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