Seller get order

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds meaningful behavioral context: PII redaction policy, the full set of data returned, and the refusal behavior for non-seller orders. This goes beyond the annotations without contradicting them.

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?

Two sentences with no fluff. The core action and scope are front-loaded, and the refusal condition is clearly stated. Every clause earns its place.

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 single-parameter read operation with annotations covering safety and no output schema, the description sufficiently explains what the tool returns and its constraints. It doesn't describe error codes or exact return format, but those are minor given the tool's simplicity and the absence of an output schema.

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% for order_id, with a clear UUID description. The description adds the semantic constraint that the order must belong to this seller, which enriches the meaning of the parameter beyond the schema. This justifies a slight bump from the baseline of 3.

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 the verb 'Fetch' and the resource 'single seller-scoped order', and enumerates the included data (buyer shipping address, items, shipment, payment status, return/dispute). It also distinguishes itself from general order fetches by emphasizing seller scope and the refusal condition, which differentiates it from siblings like orders_get and seller_list_orders.

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 a single seller-scoped order and notes it refuses if not against the seller, which sets expectations. However, it does not explicitly name alternative tools or conditions for choosing between them, though the context of sibling tools (orders_get, seller_list_orders) makes the distinction inferable.

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