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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions only that the tool is NotOffered and defers to get_orders, but says nothing about what happens if invoked, whether it errors, requires auth, or has side effects.

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 a single front-loaded sentence with no wasted words. It clearly signals unavailability first and then gives a redirect, which is appropriately concise for what appears to be a stub or disabled tool.

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 disabled-tool redirect, the description may be minimally sufficient: it tells the agent the tool is not offered and where to look instead. However, it does not explain why it is not offered, what get_orders actually returns, or whether the tool is ever usable outside the Storefront context.

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 0% and the description adds no meaning to the required order_id parameter. There is no compensation for the schema's lack of parameter documentation, so the agent gains no insight into how to fill the argument.

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 does not state what get_order_status does; it only declares 'Storefront: NotOffered' and directs the agent to get_orders. While this communicates unavailability, it lacks a functional verb+resource statement and relies on the tool name to imply purpose.

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 marks the tool as NotOffered and points to get_orders as the alternative. This gives clear guidance that the agent should not select this tool and should use get_orders instead, even though it does not specify exact selection conditions.

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