rr_get_po_pdf

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

No annotations exist, so the description carries the full burden. It implies a read operation ('get'), but does not explicitly state that it is non-destructive, nor does it disclose any authorization requirements, rate limits, or side effects. The description provides minimal behavioral context.

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 wasted words, but it is overly terse and lacks crucial details. It does not front-load the most critical information, such as return type or usage context, reducing its effectiveness.

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 lack of output schema, annotations, and any hint about return values (e.g., URL, binary data, or metadata), the description is severely incomplete. An agent cannot reasonably determine the expected output or how to process the result.

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% and the description adds no detail about the sole parameter 'po_id'. Despite the parameter name being self-explanatory, the description fails to compensate for the lack of schema annotations, leaving the agent without guidance on expected input format or constraints.

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 info for generating a PO PDF' clearly states the verb-resource relationship and hints at the output, but 'info' is vague and does not specify what exactly is returned or how it relates to PDF generation. It partially distinguishes from siblings like rr_get_po_documents but lacks specificity.

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 usage guidelines are provided. The description does not explain when to use this tool over alternatives such as rr_get_purchase_order or rr_get_po_documents, leaving the agent to infer context from the tool name only.

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