coinlore_coin

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

With no annotations, the description carries the full behavioral burden. It does not state that this is a read-only operation, whether it is rate-limited or authenticated, or what 'detailed info' includes. Only the implicit 'Get' hints at a safe read.

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?

A single efficient sentence with the verb and resource front-loaded and zero filler. It is appropriately short for a one-parameter lookup, though it leaves no room for the guidance it lacks.

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 simple one-param read tool with full schema coverage and no output schema, the description is minimally adequate. It omits what fields 'detailed info' returns and any safety/auth context, but the scope is genuinely small.

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% and the id parameter is already documented with concrete examples (90 for Bitcoin, 80 for Ethereum). The description adds nothing beyond the schema, so the baseline 3 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 verb ('Get detailed info') and resource ('a specific cryptocurrency from Coinlore'), so the agent understands it fetches one coin's details by ID. However it does not distinguish itself from close siblings like coinlore_tickers or coinlore_global, which could confuse selection.

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?

No guidance on when to use this versus coinlore_tickers (list all) or coinlore_global (market totals), nor any prerequisites. The agent must infer the single-coin retrieval context purely from the name.

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