rr_get_purchase_order

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

With no annotations provided, the description carries the full burden. It implies a read operation (get) and mentions line items, which is useful. However, it does not disclose behavior such as error handling, permissions, or rate limits. For a simple retrieval tool, this is adequate but minimal.

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 no unnecessary words. It is highly concise and efficient, focusing on the core action and result.

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 (single required parameter, no output schema), the description adequately states what the tool does and that it returns line items. However, it lacks explanation of the input parameter and does not describe return value structure or error conditions, making it only minimally complete.

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%, meaning the schema has no parameter descriptions. The description does not explain the single parameter po_id (e.g., format, required context). It only says 'Get a single purchase order with line items,' adding no value to the parameter understanding.

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 'Get a single purchase order with line items' clearly states the verb (Get) and the specific resource (a single purchase order with line items). It distinguishes itself from sibling tools like rr_list_purchase_orders (which retrieves multiple) and rr_get_po_documents/rr_get_po_pdf (which retrieve attachments).

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 such as rr_list_purchase_orders for multiple POs or rr_get_po_documents for related files. No explicit when-to-use, when-not-to-use, or prerequisites are mentioned.

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