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

Adds valuable behavioral context beyond annotations: discloses advisory-only coverage for non-bracelet categories, fabricated SKU absence, and need for manual confirmation on commercial terms. No contradictions 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?

Two concise sentences: first states core purpose, second adds critical behavioral nuance. No wasted words.

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?

Adequately describes the search tool's purpose and data quality, but given 8 parameters and no per-parameter guidance, the description lacks depth for rich filtering. Sufficient for simple queries but not for complex ones.

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 0% schema description coverage, the description only vaguely mentions searchable fields (SKU, name, material, theme) but does not explain the other parameters like limit, cursor, channel, useCases, benefitTags, which are left opaque.

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?

Clearly states verb 'search' and resource 'verified 104-SKU bracelet catalog', and distinguishes from sibling tools like crystal_get_product and crystal_list_materials by specifying catalog scope and coverage limitations.

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?

Implies usage for searching the bracelet catalog, but does not explicitly state when to use alternatives like crystal_get_product for single product lookup or crystal_build_procurement_shortlist for shortlisting.

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