Prepare Crystal Wholesale Inquiry

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

Annotations provide readOnlyHint, idempotentHint, and non-destructive flags, but the description adds specific behavioral guarantees: 'never sends, stores, or submits buyer data and never invents commercial terms.' This goes beyond annotations without contradiction.

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?

The description is two sentences long, front-loading the purpose and immediately adding key behavioral guarantees. Every sentence adds value with no redundancy.

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?

Despite having an output schema, the tool has 13 undocumented parameters and the description does not explain how to construct a valid inquiry. The agent lacks guidance on required vs optional fields, parameter interdependencies, or example usage, making the description incomplete for the tool's complexity.

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 description provides no information about any of the 13 parameters, and schema description coverage is 0%. The agent receives no help on parameter meaning, required fields, or formatting, leaving them to infer from parameter names alone.

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 explicitly states the tool 'validates bracelet SKUs and drafts an English wholesale inquiry,' providing a specific verb and resource. This clearly distinguishes it from siblings like crystal_search_products or crystal_build_procurement_shortlist.

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 mentions the tool is 'read-only' and 'never sends, stores, or submits buyer data,' implying safe usage without side effects. However, it does not explicitly state when to use this tool over alternatives or when not to use it.

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