GetOrderIndex

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

No annotations provided, so description carries the full burden. The only behavioral trait disclosed is deprecation. There is no mention of side effects, authorization requirements, or rate limits. Critical transparency gaps given no structured annotations.

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 very short (two words plus deprecated tag). It is efficient with no wasted words, but front-loading is null due to deprecation label. Could be improved with more context, but conciseness is appropriate.

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 and simple nature, the description fails to explain what 'actions' means, the data format, or how to interpret the response. A deprecated tool still needs sufficient context for an agent to handle it correctly.

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 description coverage is 100% (no parameters). Description does not add param-specific meaning, which is acceptable. Baseline of 3 applies; no additional value or detriment.

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 states it is deprecated and 'Get all actions you can do on the order API'. This indicates a specific resource (actions on order API) but is vague about what 'actions' means. It distinguishes from siblings like GetOrder which retrieve specific orders, but the purpose is still ambiguous.

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 guidance on when to use this tool vs alternatives. The deprecation note implies it should not be used, but no alternative is mentioned. This leaves the agent without context on whether to invoke it.

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