Get Mouser order history

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description contributes the mutual-exclusivity constraint on parameters, which is genuinely behavioral, but says nothing about result volume, pagination, or limits on how many orders come back.

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?

Two sentences, front-loaded with purpose, then the constraint. Every clause carries information an agent needs; nothing is repeated from the schema or annotations.

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 five-parameter read-only list tool with no output schema, the definition covers what the agent needs to construct a valid call. The remaining gap is any indication of result-set size or how to retrieve the full history.

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?

With only 40% schema description coverage and zero required parameters, the description does the crucial work the schema cannot: it enforces that exactly one lookup mode be used and that startDate/endDate are a paired unit. It also supplies a concrete dateFilter example ('LastMonth') for an enum the schema leaves undocumented.

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 opens with a specific verb and resource ('Lists past Mouser orders'), which distinguishes it from get_order (singular) and from the parts/cart siblings. It stops short of naming those siblings explicitly, so the differentiation is implied rather than stated.

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 gives a concrete invocation rule -- 'Give exactly one lookup' -- and enumerates the four mutually exclusive lookup modes, including that startDate and endDate must be supplied together. What is missing is guidance on when to choose this tool over get_order or how to request everything (the 'All' dateFilter is never mentioned).

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