Search Crystal Products

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint, and openWorldHint. Description adds useful behavioral specifics: pricing, MOQ, inventory, lead time, and certificates are never inferred. This exceeds annotation coverage.

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, no unnecessary words. Critical information is front-loaded (search scope) and limitations stated succinctly.

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?

Complexity is moderate with 8 parameters and an output schema. Description covers core functionality, scope boundaries, and data limitations. Pagination is left to schema, which is acceptable given the output schema exists.

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%. Description explains search-by fields (SKU, name, material, theme) which maps to the query and materials parameters, but omits pagination (limit, cursor) and filter-by useCases/benefitTags. Partial compensation.

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?

Description specifies a concrete action: searching a verified 104-SKU bracelet catalog by SKU, name, material, or theme. It clearly distinguishes from siblings by noting that beads, accessories, and raw materials return advisory-only coverage.

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?

Provides clear when-to-use guidance (for bracelet catalog) and when-not (advisory for others). Context signals mention sibling tools like crystal_get_product for specific lookups, reinforcing the tool's niche.

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