Place an order for a pet.

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

The description only states 'Place a new order', which implies a mutation, but does not disclose side effects, required permissions, or response behavior. Annotations provide only openWorldHint, which does not cover safety traits, so the description carries the burden and fails to add behavioral transparency beyond the basic verb.

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 sentence with no filler; it is front-loaded and every word serves a purpose. While it is under-specified, that is an issue of completeness rather than conciseness, so it earns a perfect score here.

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 tool with 6 parameters, no output schema, and minimal annotations, a one-sentence description is grossly insufficient. It doesn't explain what an order is, how petId relates to the order, or any order lifecycle details, making it inadequate for real-world invocation.

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?

With schema description coverage at only 17% (only 'status' has a description), the description needed to compensate by explaining parameters, but it mentions none at all. It provides zero guidance on id, petId, quantity, shipDate, or complete, leaving the agent completely blind to parameter semantics.

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 a specific action ('Place a new order') on a specific resource (order in the store), distinguishing it from sibling get/delete operations. However, it omits pet-specific context from the title and doesn't explicitly contrast with alternatives, preventing a perfect score.

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 get_inventory or delete_order. It lacks prerequisites, exclusions, or contextual hints beyond the bare action itself, leaving agents to infer usage from the tool name alone.

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