loki_get_order

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

Annotations already declare readOnlyHint=true and openWorldHint=true, indicating a safe, non-destructive operation. The description adds valuable behavioral context about the input format (internal id vs PO string), which is not conveyed by annotations. No contradictions found.

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?

The description is extremely concise—two sentences plus a critical note. Every part is purposeful, and the important warning is highlighted with 'IMPORTANT', making it easy for an agent to parse quickly.

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?

Given no output schema, the description does not specify the return format, but 'full detail' implies comprehensive data. The input requirements are fully covered. Minor gap: no mention of return structure, but overall adequate for usage.

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 provides a minimal description of order_id. The tool description significantly enriches this by clarifying the id's origin, format, and relationship to PO strings, including concrete examples. This goes well beyond the schema's description.

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 explicitly states 'Get full detail for a single order', using a specific verb and resource. It further distinguishes from sibling tools by specifying the unique input requirement (internal numeric id vs PO string), making its purpose clear and differentiated.

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 provides explicit when-to-use guidance (when you have an internal numeric id) and what to do if you don't (run loki_search_orders first). It directly names an alternative tool and the prerequisite action, leaving no ambiguity.

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