rr_get_po_documents

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

No annotations provided, so the description carries full burden. It only states 'list documents' without disclosing if the operation is read-only, what permissions are needed, or if there are any side effects. The return format (e.g., document IDs, URLs) is not mentioned, leaving the agent uninformed about 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?

One short sentence, front-loaded with verb and resource. It's efficient but could include slight additional detail (e.g., what fields are returned) without becoming verbose. Concise and to the point.

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 simple list tool with one parameter, the description provides the basic purpose. However, without an output schema, the agent doesn't know the format or content of the document list (e.g., names, IDs, URLs). This gap reduces completeness. Adequate but not fully informative.

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 single parameter 'po_id' is clearly implied by the description as the purchase order identifier. While schema coverage is 0% (no description in schema), the description adds sufficient context for the parameter's meaning. This compensates well for the lack of schema documentation.

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 specific verb 'List' and resource 'documents attached to a PO', clearly distinguishing from siblings like rr_get_po_pdf (which returns a PDF document) and rr_get_purchase_order (which returns PO details). The purpose is unambiguous.

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?

No guidance on when to use this tool compared to alternatives. No exclusions, prerequisites, or context about whether it requires a specific status or if the PO must exist. The agent lacks hints for appropriate usage.

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