Orders: verify code

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

Description adds that it is a read check (consistent with readOnlyHint and destructiveHint annotations) and details response statuses (success, fail, expired, attempts). This goes beyond annotations to inform agent of possible outcomes.

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?

Three concise sentences, front-loaded with core function. No wasted words; every sentence provides essential 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?

Despite no output schema, description explains response statuses, which is critical for agent to interpret results. Tool is simple with two parameters; description fully covers usage and outcomes.

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 100% with parameter descriptions. Description adds minimal context about the buyer stating the code, but agents can infer parameter roles from schema. Baseline 3 is appropriate.

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?

Description clearly states it verifies a confirmation code for order pickup, with specific verb 'Verifies' and resource 'confirmation code'. It distinguishes from delivery domain sibling tool, making purpose 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?

Explicitly states when to use (handover at pickup point) and warns against confusing with delivery_check_confirmation_code, providing clear alternative. Also notes it's a read check, guiding appropriate usage.

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