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

Annotations already establish readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: fixed page size of 100, the return shape (part numbers and descriptions with paging info), and the explicit limitation that availability/price are not included.

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?

Three tight sentences with the core operation, page size, and return shape front-loaded. Every sentence carries distinct information (what it does, what it returns, what it deliberately does not return).

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 two-parameter read-only listing tool with no output schema, the description covers action, scope, page size, and return fields, which is close to sufficient. It could have stated the ordering of results or what happens past the last page, but nothing essential for invocation is missing.

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 coverage is 100%, so the baseline is 3, but the description meaningfully extends the page parameter by disclosing the fixed 100-items-per-page window and confirms the single-family scope of the required family argument. That is real added meaning for pagination decisions beyond the schema's '1-based page number'.

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 specific verb and resource (page through catalog parts) plus the scoping constraint (one equipment family) and page size (100 per page). It is clearly a bulk listing operation, distinct in spirit from lookup_part, but it never explicitly names or contrasts a sibling the way the strongest definitions do.

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?

Usage is implied: browse a family's catalog when you need part numbers/descriptions. The final sentence, 'Availability and price are quoted per application,' is a useful implicit routing hint that this tool is not the place to get pricing, but it never says so directly or names request_quote as the alternative.

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