order_get

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

Description adds context beyond annotations: the PII stripping behavior via the include_pii parameter is explained. Annotations already provide readOnlyHint, destructiveHint, idempotentHint, but the description clarifies the default PII handling, adding 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?

Single sentence that is concise and front-loaded with the core purpose. Every word adds value; no redundant or vague phrasing.

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?

Lacks explanation of return values, error handling, or authentication. No output schema is provided, so the description could have mentioned what fields are returned. However, it covers the essential read-only and PII behavior, making it moderately complete for a simple retrieval tool.

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?

Only the include_pii parameter has a description in both schema and tool description, with redundant content. Site and order_id are not explained in the description. With schema coverage at 33%, the description fails to provide necessary context for these two required parameters.

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 retrieves a single order by ID, using a specific HTTP GET endpoint. It distinguishes itself from the sibling 'orders_list' by specifying a single order rather than a list.

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?

Implied usage (fetch a single order by ID) but no explicit guidance on when to use vs. alternatives (e.g., orders_list) or when not to use this tool. No mention of prerequisites or exclusion criteria.

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