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

Discloses AI call to Grok, cost of $0.10/call, and use of Father's curated database. No annotations exist, so description carries full burden; it adequately informs about premium nature and data sources.

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?

Front-loaded with action and returns, then appends use cases and pricing. Slightly verbose with embedded URL and parentheses, but overall well-structured.

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 input, output (detailed list), cost, use cases. No output schema, so description fully compensates. Adequate for an agent to invoke correctly.

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 100%, so baseline is 3. Description adds context (GemHunt, UUID or numeric) but no additional meaning beyond schema.

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 ('trigger an appraisal') and resource ('single gem on GemHunt'), lists specific outputs (value, confidence, etc.), and distinguishes from sibling tools like 'alya_gems_recent' which lists gems.

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 explicit use cases (collectibles agents, jewelry e-commerce, insurance, due diligence) but does not mention when not to use or alternatives.

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