GetOrder

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states what data is retrieved but fails to mention any side effects, authentication requirements, or rate limits. For a read operation, the lack of disclosure is a gap.

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 (single sentence) but includes unnecessary repetition ('[DEPRECATED] DEPRECATED'). While concise, the redundancy reduces clarity. A cleaner version would be more effective.

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 tool with no parameters and no output schema, the description provides the basic purpose. However, it lacks details on what 'full Order' entails (e.g., fields returned), and the deprecation should ideally point to a replacement. This leaves the agent somewhat underinformed.

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 has zero parameters, and according to guidelines, the baseline is 4. The description does not need to add parameter meaning since there are none, and it correctly conveys the tool's purpose without requiring additional parameter context.

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 retrieves full Order and Order Item properties, which is a specific verb and resource. However, it does not differentiate itself from sibling tools like GetOrderV3 or GetOrderListFull, and the deprecation notice is redundant ('[DEPRECATED] DEPRECATED').

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 only marks the tool as deprecated but provides no guidance on when to use it versus alternatives such as GetOrderV3. An explicit recommendation for an alternative is missing.

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