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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful behavioral context beyond annotations: the catalog includes pricing, the result set is the full catalog, and the returned material IDs are explicitly compatible with get_estimate. No contradiction with 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?

Three sentences with no wasted words: the first states the resource and scope, the second gives the key filtering instruction, and the third provides integration guidance. It is front-loaded, concise, and every sentence earns its place.

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?

The description is complete enough for a read-only catalog tool: annotations cover safety, the schema covers all parameters, an output schema is present, and the description adds pricing and get_estimate compatibility context. The only notable gap is the lack of explicit guidance on when to prefer get_material_options.

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 100% description coverage for limit, offset, search, and category, so the schema does the heavy lifting. The description only restates the category filter and does not add deeper parameter semantics, which lands it at the baseline of 3.

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 a specific verb and resource: 'Browse the full material catalog with pricing,' and it lists the covered materials. It does not explicitly contrast this with sibling tool get_material_options, so it loses one point on sibling differentiation.

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 implies when to use it — for browsing the full catalog, filtering by category, and getting material IDs for get_estimate. However, it never explicitly names get_material_options as an alternative or states when not to use this tool, so the routing guidance is only implicit.

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