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

The annotation destructiveHint=true directly contradicts the description 'Add a new pet to the store,' which describes a creation operation, not a destructive one. The description adds no behavioral context beyond this, and the contradiction makes the behavioral profile unreliable for an agent.

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 clearly states the action and target resource. Every word earns its place, and there is no redundant filler or unnecessary detail.

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 zero-parameter tool with an output schema, the description is minimally adequate for understanding the core operation. However, it lacks behavioral context, usage guidance, and fails to reconcile the contradictory destructiveHint annotation, so it is not fully complete for an agent deciding when and how to invoke it.

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 with no required or optional parameters, so there is nothing for the description to document. Per the baseline for zero-parameter tools, the description does not need to add parameter details, and it does not harm clarity.

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 a specific verb and resource, 'Add a new pet to the store,' making the tool's purpose immediately clear and distinguishing it from siblings like updatePet, deletePet, and findPetsByStatus. The word 'new' reinforces that this is a create operation.

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 gives no guidance on when to use this tool versus alternatives. It does not mention that updatePet should be used for modifying existing pets, nor does it state any prerequisites or exclusions. The usage context is only implied by the phrase 'Add a new pet.'

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