getCoinEvents

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

Discloses read-only nature, authentication requirement ('No API key required'), and parameter details (limit caps). No annotations exist, so the description carries the full burden. Could improve by noting response format or error behavior, but adequate for a simple read tool.

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?

Two sentences, each sentence provides essential information without redundancy. Purpose and usage are front-loaded. No unnecessary words.

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?

Given no output schema, the description mentions 'dates and descriptions', which hints at return structure. For a tool with only 2 parameters and a straightforward purpose, this is largely complete. Could explicitly state that the response will be an array of event objects, but not required.

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%, so baseline is 3. The description adds value by explaining coinId format (canonical slug, not ticker) with examples, and clarifies limit default and max. This goes beyond the schema descriptions.

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 identifies the action ('Get the timeline of events for a coin'), the resource ('events like launches, partnerships, hard forks, conference talks'), and distinguishes from the sibling getTickersById by specifying it is for events, not prices.

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?

Explicitly states when to use ('what is happening with X', 'upcoming events for Ethereum') and when not to ('For prices use getTickersById'), providing clear guidance and an alternative tool.

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