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

No annotations are provided, so the description carries the full behavioral burden. "Get" implies a read, but it discloses nothing about permissions, behavior for an unknown order_id, error handling, or what "next_action" contains.

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?

It is certainly short and front-loaded, but this is under-specification rather than tight writing — a four-word fragment that omits nearly all decision-relevant content.

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 simple single-parameter read tool this could be adequate, but with no annotations and no output schema, the description should at least explain the returned payload and the "next_action" field. Neither is defined.

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?

The schema has 0% description coverage for order_id and the description adds no meaning about its format, source, or constraints. With one undocumented required parameter and no compensating text, the description does not fill the gap.

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?

"Full order incl. next_action" states the resource and implies scope beyond a status-only lookup, which faintly distinguishes it from sibling get_order_status. However, "next_action" is unexplained jargon and the description never clearly asserts it returns the order record.

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?

No statement of when to use this versus get_order_status, get_order (siblings cancel_order, create_order, list_rp, etc.) or any alternative. Usage must be inferred entirely from the tool name.

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