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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the lookup spans both quote requests and orders, but says nothing about auth needs, rate limits, or lookup-failure behavior. Modest added value on top of 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?

A single front-loaded sentence with no wasted words. It is sized correctly for a one-parameter read tool, though it is minimal enough that it could have afforded one more clarifying clause.

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 single-parameter read operation with annotations covering the safety profile and no output schema required in the description, this is nearly complete. The only shortfall is the absence of any lookup-failure or result-shape 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%, so the description must compensate for the single parameter. 'By its reference' does give the parameter's semantic role, but it adds no format, type, or example detail. Adequate but thin given the zero coverage.

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?

States a clear verb+resource ('Check the status of a custom quote request or order') and names the lookup key ('by its reference'), which separates it from the list-type siblings like quote_list. It could be sharper about the odd mismatch between the tool name (rush_order_status) and the quoted breadth (quote requests AND orders).

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?

It implies the usage precondition (you must have a reference) but never says when to pick this over quote_list or request_quote, nor any exclusions. That is the same level of guidance as the MID calibration example, which scored 2.

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