get_order

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

No annotations provided, so description carries full burden. States 'Get' implying read-only safety, but provides no details on error behavior (e.g., 404 for invalid ID), cache behavior, or what constitutes 'detailed' information beyond the order ID parameter.

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 front-loaded sentence of 10 words with zero redundancy. Every word earns its place: verb, resource scope, and key parameter reference.

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?

Adequate for a single-parameter retrieval tool with complete schema coverage. Acceptable given no output schema exists, though could benefit from noting that the ID must be known (likely from list_orders) and hinting at the data richness expected.

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 has 100% description coverage ('The work order ID'), so baseline is met. Description mentions 'by its ID' but adds no additional semantics regarding ID format, constraints, or lookup requirements beyond the schema definition.

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?

Clear verb 'Get' with specific resource 'work order'. Scope qualifiers 'single' and 'by its ID' effectively distinguish this from sibling list_orders, though 'detailed information' is vague about what data is returned.

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?

Implicitly signals ID-based lookup via 'by its ID', distinguishing from list/search siblings. However, lacks explicit guidance on when to use list_orders first to find IDs, or error handling if ID is unknown.

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