agentscoin_price

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

Annotations declare readOnlyHint=false and destructiveHint=true without explaining why; the description supplies the reason (a per-call charge paid automatically from the saved wallet), which is real added context about cost and auth. It still omits failure/refund behavior and whether the charge occurs before or after a successful fetch.

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 short sentences with zero waste; the action is front-loaded and the cost constraint follows immediately.

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?

With no output schema, the description is not obliged to describe return values, and the cost/wallet behavior is the key operational fact for this tool. Missing only minor edges such as what happens if the wallet balance is insufficient.

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 both 'symbol' and 'privateKey'. The description's mention of paying 'from your saved wallet' loosely reinforces the default privateKey path but adds no format or override detail beyond the schema.

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+resource ('Get a live crypto price') and qualifies it as premium data, which separates it from generic info siblings like agentscoin_token_info. It does not explicitly name or contrast any sibling, so it stops short of a 5.

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?

Usage is implied rather than stated: the cost disclosure ('0.1 AGENT per call') tells the agent this is a paid path, but there is no guidance on when to prefer it over agentscoin_token_info or other data tools, and no exclusions or failure guidance.

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