Get Crystal Product

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

Annotations already declare read-only, idempotent, non-destructive. Description adds return details (materials, source URL, etc.) but no additional behavioral traits like auth requirements, rate limits, or side effects.

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?

Single sentence is efficient and front-loaded, but could be slightly more structured (e.g., listing return fields). 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?

Covers core purpose and explicit return fields, supported by output schema. Missing error handling or authentication context, but sufficient for a simple read operation with good annotations.

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 has 0% description coverage; description states parameters are for exact match by SKU or slug. However, it doesn't clarify if both can be provided, which takes precedence, or that exactly one is required. Adds basic meaning but lacks full clarity.

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 clearly states verb 'Get', resource 'one verified bracelet', and identification method 'by exact SKU or slug'. It specifies what is returned (materials, source URL, related products, confirmation status). Distinct from sibling tools like crystal_search_products which handle searches.

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 when exact SKU or slug is known, but no explicit guidance on when to use this tool versus alternatives like crystal_search_products. No when-not-to-use or prerequisite conditions mentioned.

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