petstore-api.getOrderById

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

Annotations declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, which fully cover the safety profile. The description adds the specific behavior of retrieving an order by ID, which is consistent with annotations. It could add more context like return format, but with strong annotations, the description adds sufficient transparency.

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 fluff, which is efficient. It is front-loaded with the action and resource. However, it is extremely brief and lacks any additional context, but for a simple lookup tool, this is acceptable. A 5 might include a bit more detail on the ID parameter, but this is near-optimal.

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 tool's simplicity (0 params, unchanged safety profile, output schema exists), the description is adequate. It does not explain how the ID is provided, which is a gap, but the presence of an output schema and strong annotations compensate. The description could be more complete by noting the ID requirement, but it is not incomplete for basic usage.

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?

Although the schema shows zero parameters, the description implies a parameter (order ID) that is not in the schema. This is a mismatch, but the description does not explain how the ID is passed. However, since schema coverage is 100% and parameters are 0, the description provides the minimal necessary meaning. Baseline 4 is appropriate for 0 parameters.

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 verb 'Find' and the resource 'purchase order by ID', which is specific and aligns with the tool name. It does not explicitly differentiate from the sibling 'getPetById' but the resource is distinct enough. A 5 would require explicit differentiation, but the purpose is clear.

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 explicit guidance on when to use this tool versus alternatives, but the context of retrieving a purchase order by ID is self-evident. It lacks any exclusion criteria or mention of alternatives like 'getPetById'. The agent can infer usage from the name and description, but no explicit guidelines are provided.

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