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

With no annotations present, the description carries the full burden of behavioral disclosure. It does this well by stating that ratings are opinions derived from disclosed market inputs and are never predictions or financial advice. It also discloses the breadth of the response and its risk-related content, which is useful behavioral context beyond the schema.

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?

Three sentences with no repetition of schema or annotation data. The first sentence is long but packed with a purposeful enumeration of what the profile includes, and the usage and disclaimer sentences each earn their 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 single-parameter tool with no output schema, the description fully covers what the agent can expect: price data, rating breakdown, confidence, risk read, market figures, links, and the opinion/non-advice caveat. Nothing essential is missing for correct selection and invocation.

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 the schema already documents the coin parameter thoroughly. The description adds the idea that this is about 'one coin' and links the parameter to user intent, but it does not need to add more parameter-level detail.

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 opens with a specific verb and resource: it returns what CoinGraph holds on one coin, then enumerates the exact content areas. It clearly separates this from sibling tools like coingraph_compare or get_survival_rating by emphasizing the single-coin, comprehensive nature.

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?

It gives explicit when-to-use guidance: when a person asks what is happening with a coin or whether the project is still going. It does not name alternatives or exclusions, so it misses the 'when not to use' component, but the context is still clear.

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