purchase_order

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false. The description adds the list of operations (some mutating) and the return format (JSON with data or error). However, it does not describe side effects, permission requirements, or behavioral nuances beyond annotations. The description adds moderate value.

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 concise and well-structured. It front-loads the purpose, then lists operations and arguments in a clear, bullet-like format. Every sentence adds value, and there is no wasted text.

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 complexity (8 parameters, multiple operations, output schema exists), the description is fairly complete but lacks operation-specific parameter requirements. It does not detail the output structure (though output schema exists) or error handling beyond a generic error response. More guidance on operation-specific parameter needs would improve completeness.

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 coverage is 0%, so the description must compensate. It explains each parameter: operation (list of operations), pk (PO ID), data (dict for create/update), location_id (receiving location), items (line items example), search, limit, offset. This adds significant meaning beyond the bare schema types. However, it could clarify which parameters are required for each operation.

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 clearly states it is for 'Purchase order lifecycle management', lists all operations, and distinguishes itself from sibling tools by its specific domain (purchase orders vs sales orders, etc.). The verb 'manage' plus resource 'purchase order' is specific and 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?

The description provides a list of operations and arguments but does not explicitly state when to use this tool versus sibling tools (e.g., sales_order, return_order). It implies usage through the resource name but lacks explicit when-to-use and when-not-to-use guidance.

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