petstore-api.addPet

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

The description says 'Add a new pet' which is a creation operation, but annotations declare destructiveHint=true, creating a direct contradiction. No additional behavioral context is provided about side effects, permissions, response behavior, or failure modes, so the description fails to disclose its true behavior.

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 with zero filler. Every word earns its place; it is appropriately concise for a simple one-line tool description.

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 is simple and has an output schema, but the description omits usage guidance and fails to resolve the conflict with destructiveHint. An agent cannot reliably determine when to invoke this tool or what side effects to expect, making the overall context incomplete.

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 and 100% coverage, so there are no parameter semantics for the description to clarify. The baseline of 4 applies because no parameter information is needed.

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 ('Add') and resource ('a new pet to the store'), making the operation clear and distinguishing it from siblings like updatePet and deletePet. It loses one point because it does not differentiate itself from the near-duplicate swagger-petstore addPet tool.

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?

There is no guidance about when to use this tool versus alternatives. 'New pet' weakly implies it is not for updates or deletes, but there is no explicit when/when-not or mention of alternative tools, prerequisites, or error cases.

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