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 discloses a key behavioral trait (returns full line item detail), which is useful context beyond the tool name. However, it does not mention any other behavior such as error handling, access requirements, or response structure, which is a notable gap for a tool without an output schema.

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 filler. It efficiently communicates the tool's core purpose and differentiator without wasting words.

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 get operation, the description provides sufficient context: it identifies the entity type, indicates singular retrieval, and mentions that full line item details are included. While there is no output schema, the description partially covers what is returned. It is not exhaustive, but it is adequate for this tool's complexity.

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 input schema already describes all three parameters with 100% coverage, so the description is not required to add parameter details. The description does not reference parameters at all, but the baseline of 3 applies because the schema handles the heavy lifting.

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 a specific verb ('Get') with a clear resource ('a single Acumatica purchase order') and adds distinguishing detail ('with full line item detail'). This effectively differentiates it from sibling tools like query_purchase_orders (which implies listing/filtering) and get_sales_order or get_shipment (which are for different entities).

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 usage for retrieving one specific purchase order (as opposed to querying multiple), but it does not explicitly state when to use this over alternatives like query_purchase_orders. It provides context but no exclusions or direct alternative references, so it earns a 3 for implied usage.

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