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

With no annotations, the description carries the transparency burden. It discloses the premium nature, the micropayment requirement via MPP, and the data source, which are critical behavioral traits. It does not mention failure modes or rate limits, but the disclosed payment prerequisite is significant.

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 a single, information-dense sentence. It front-loads 'PREMIUM' to signal cost/special status, then packs the return contents, payment requirement, and data source without redundancy or filler.

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 no output schema, the description thoroughly enumerates what the breakdown includes (8 metric scores, explanations, special scoring rules, valuation reasoning, ranking context), plus the MPP requirement and source. This gives an agent enough to set expectations and compare against sibling tools.

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 coverage is 100%, and the schema already documents `coin` and `_meta` with examples. The description adds no new parameter-level detail, so it neither compensates nor detracts. Baseline 3 is appropriate because the schema does the heavy lifting.

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 clearly states a specific action ('Returns a complete fundamental analysis') on a resource ('a cryptocurrency') and enumerates the distinct content (all 8 metric scores, explanations, special scoring rules, valuation reasoning, ranking context). This differentiates it from sibling tools like get_tvr_score or get_comparison_report.

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 gives clear context ('PREMIUM', requires micropayment, provides a full breakdown) but does not explicitly name alternative tools for when a lighter analysis is needed. The 'complete fundamental analysis' implication guides usage, but no direct contrasting guidance appears.

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