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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description still adds meaningful behavioral context beyond them: it is a record not a rating, it links each line to evidence, and it returns weekly change tags plus 7-day high/low/latest price. No auth, rate-limit, or freshness semantics are described, keeping it short of a 5.

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 content is front-loaded with the four-group structure and the usage trigger follows immediately. It is, however, a dense run-on first sentence with stacked parentheticals, and the measurement clause duplicates information that the exit_cost sibling tool owns, so a small amount of text could be trimmed.

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?

With no output schema, the description carries the burden of describing returns, and it does so well: four fixed groups, evidence links, weekly change tags, and 7-day high/low/latest price. It does not explain response format beyond that or how 'not established' is represented, leaving minor gaps for a data-heavy read tool.

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?

There is a single 'token' parameter and schema description coverage is 100%, with example values ('USDC', 'pepe', '0x8335…') already in the schema. The description adds nothing about how ticker vs name vs contract address are resolved or matched, so the baseline 3 for a fully documented schema applies.

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?

States a specific resource (the CM Profile of a tracked coin) broken into four named groups, so the agent knows exactly what the tool returns: established facts, measurements, sourced writing, and unestablished items. The closing line 'A record, not a rating' further pins down that this is descriptive data rather than an evaluative score, differentiating it from the exit_cost/exit_index siblings.

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?

Gives explicit triggers: 'Use this when someone asks what is known about a coin, how well documented it is, or whether it depends on a company.' That is clear context for selection, but it names no siblings (exit_cost, exit_index, search) and gives no when-not-to-use conditions, despite the description admitting it also returns sell-cost data that overlaps with exit_cost.

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