get_purchase_order

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

No annotations are provided, so the description carries full burden. It only says 'Retrieve', implying a safe read operation, but does not disclose error behavior (e.g., what if ID doesn't exist), response format, or any side effects. This is insufficient for a tool with no annotation coverage.

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 that directly conveys the core purpose. It is concise and front-loaded with the key action. However, it could be slightly more detailed without becoming verbose.

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?

Considering the tool is simple (1 param, no output schema, no annotations), the description is minimal. It covers the basic what but lacks completeness for a standalone description. No hints on error handling, return values, or integration with other tools. Adequate for a trivial tool but not fully self-sufficient.

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?

Schema description coverage is 0%, so the description must compensate. It mentions 'by its unique ID', which adds minimal context that the id parameter is the purchase order ID, but does not explain where to find the ID, format constraints, or any other useful detail. Falls short of the baseline 3 for low coverage.

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 it retrieves a purchase order by ID. Verb 'Retrieve' and resource 'purchase order' are specific, and the method 'by its unique ID' is unambiguous. However, it does not differentiate from sibling tool list_purchase_orders, which might return multiple orders.

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 implies that the tool is used when you have a specific purchase order ID, but it does not explicitly state when to use this tool over alternatives like list_purchase_orders. No guidance on when not to use or prerequisites.

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