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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'Get' implies a read-only operation, the description doesn't address important behavioral aspects like rate limits, data freshness (how current is 'current'), error conditions, or authentication requirements. For a tool with zero annotation coverage, this represents a significant gap in transparency.

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 perfectly concise - a single sentence that states exactly what the tool does without any wasted words. It's front-loaded with the core functionality and contains no redundant information. Every word earns its place in this minimal but complete statement of purpose.

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 tool with no annotations, no output schema, and 0% schema description coverage, the description is inadequate. While concise, it doesn't provide enough information about behavior, parameter usage, or return values. The agent would need to guess about important aspects like response format, error handling, and parameter constraints.

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?

The schema has 0% description coverage, with one undocumented parameter 'symbol'. The description mentions 'cryptocurrency' which provides some context for what 'symbol' might represent, but doesn't specify format (e.g., 'BTC', 'bitcoin', ticker symbols), valid values, or examples. This minimal compensation for the complete lack of schema documentation is insufficient.

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 the action ('Get') and resource ('current price of a cryptocurrency'), making the purpose immediately understandable. It's specific enough to distinguish this tool from potential alternatives like historical price tools or exchange rate calculators. However, it doesn't explicitly differentiate from non-existent siblings, so it doesn't reach the highest score.

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 provides no guidance on when to use this tool versus alternatives, prerequisites, or limitations. It simply states what the tool does without context about appropriate use cases or constraints. Since there are no sibling tools mentioned, this omission is less critical but still leaves the agent without usage context.

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