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

No annotations are present, so the description carries the full burden. It discloses the output composition (score, verdict, every metric value, link) and notes the analysis is 'free', but it does not explicitly state the tool is read-only, has no side effects, or mention rate limits or error behavior. The output detail is useful, but the side-effect profile is left implicit.

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 that front-loads the purpose ('Free analysis of a crypto-asset') before detailing the scoring checklist and outputs. The list of 10 metrics is long but useful for setting agent expectations about returned data, so every part earns its place.

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?

For a one-parameter tool with no output schema, the description explains what is returned (score, verdict, metrics, link) and the scoring methodology, which is sufficient for an agent to understand the result. It does not mention error cases like unknown symbols or data freshness, but those are minor given the tool's simplicity.

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% for the single 'symbol' parameter, so the schema already documents it. The description does not add any additional meaning about the parameter itself, just contextualizes the tool's purpose. With full schema coverage, the baseline of 3 is appropriate.

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 states exactly what the tool does: it analyzes a crypto-asset, scores it against a 10-point checklist, and returns score, verdict, metrics, and a link. The resource type (crypto-asset, coin or token) clearly distinguishes it from sibling tools analyze_etf and analyze_stock, so an agent can tell them apart without opening schemas.

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 clearly scopes the tool to crypto-assets (coin or token), which provides unambiguous context for when to use it. However, it does not explicitly mention alternatives or exclusions like 'for stocks use analyze_stock', relying on the sibling names and asset type to route the agent. This is clear context without explicit when-not/alternative guidance.

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