loki_get_order_timelines

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds value by explaining the output is a chronological timeline and warns about the id type. No contradictions. A small deduction because the description could mention pagination or format, but overall good.

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 concise: two core sentences plus a highlighted warning. It is front-loaded with purpose, then usage, then parameter detail. Every sentence serves a purpose with no waste.

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 the tool has one parameter and no output schema, the description is complete. It explains the tool's function, when to use it, and the exact input required. No missing information.

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 input schema describes order_id as 'The internal numeric order id.' The description adds crucial context: it is the id from loki_search_orders, not the PO string. This extra meaning helps the agent select the correct value.

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 tool gets the status/event timeline for an order, specifically the chronological history of state changes. It uses a specific verb and resource, and the purpose is distinct from sibling tools like loki_get_order (single order snapshot) and loki_search_orders (search).

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 explicitly says it is useful for debugging 'why is this order stuck/late', providing clear context for when to use it. It also contrasts the required input (internal numeric id) with the PO order_id string, helping the agent avoid misuse.

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