upsert_purchase_order

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

No annotations provided, so the description carries full burden. It discloses critical behavioral traits: legacy status, immediate write behavior, high risk, and bypassing the INFLOW_ENABLE_SAFE_WRITES safety mechanism. Missing details on concurrency (timestamp param), idempotency, or what happens on partial failures.

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?

Very concise two-sentence structure with critical warning front-loaded in brackets. Every sentence earns its place and directs immediate action.

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 12 parameters with complex nested objects (items array, shipping address) and no output schema, the description provides essential context about the tool's risk and preferred alternative. Missing behavioral details around concurrency control (timestamp) and failure modes, but the warning adequately alerts agents to avoid this path.

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% for all 12 parameters including nested items object. The description adds no parameter-level details beyond what the schema provides. Baseline 3 is appropriate when schema does all documentation work.

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 states a specific verb (upsert = create or update) and resource (purchase order), and explicitly scopes it as a legacy immediate write. It clearly distinguishes itself from the preferred 'set_purchase_order' alternative. A 5 would require additional scope details beyond what the schema already provides.

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?

Explicitly names the preferred alternative tool ('set_purchase_order') and warns to avoid this tool due to high risk. Clear directive that this is a legacy path. Nothing left to inference.

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