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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Deletes a pet.' only implies a destructive action but does not disclose consequences (e.g., irreversibility), authentication requirements, or scope of deletion (e.g., does it cascade to related data?). This is insufficient for a delete operation.

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 short but redundant with two identical statements. It is under-specification rather than concise, as it fails to include necessary information about parameters or behavior. Every sentence is repeated, with no added value.

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?

The tool has 3 parameters, no output schema, and no annotations. The description fails to explain any of these aspects. It does not mention required parameters, return values, error conditions, or any operational context. The description is completely inadequate for an agent to correctly invoke this tool.

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 description adds no meaning beyond the input schema. Schema description coverage is 0%, and the description does not mention petId, api_key, or x-hapi-auth-state. The agent receives no explanation of what these parameters mean, how they relate, or any format details.

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 'Deletes a pet. - Delete a pet.' is a tautology that merely restates the tool name 'deletePet'. It adds no specificity about scope, nuances, or what distinguishes it from sibling tools like deleteOrder or deleteUser beyond the resource name.

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, nor any context about prerequisites, conditions, or exclusions. There is no mention of when deletion is appropriate or what precautions should be taken.

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