Get Purchase Order

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds behavioral specifics: 'full detail (including line items)', the configurable response_format with default markdown, and the return fields (vendor, warehouse, dates, line products).

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 compact: a one-sentence purpose, a brief args list, and a return line. It is well-structured and every sentence adds information.

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 2-parameter schema, no output schema, and strong annotations, the description covers the essential aspects: what it returns, the line items, and output format. It lacks only edge-case behavior (e.g., not found), but that is not required for a simple GET-like tool.

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 100%, so the schema already documents both parameters sufficiently. The description restates the params but adds only the provenance hint for identifier and confirms the default output format, which adds marginal value.

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 opens with a specific verb+resource: 'Get full detail (including line items) of one purchase order by its identifier (UUID).' This clearly distinguishes it from sibling list/receive/create tools, which operate on collections or different actions.

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 mentions the identifier comes 'from logiwa_list_purchase_orders', giving a usage context. It does not explicitly name alternatives or exclusions, but it clearly implies use for single-PO detail retrieval, which is sufficient context.

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