My coin watches

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, and idempotentHint=false. The description adds useful behavioral context beyond those annotations: it requires a Toll key, never exposes the secret, and explains that paused status occurs after 5 failed deliveries.

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 compact and front-loads the resource before listing fields and requirements. The semicolon-separated field list is dense but every clause carries useful information; only minor structural improvement would make it more scannable.

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 zero-parameter read-only listing with no output schema, the description supplies the key return fields (id, token, url, paused, fails, last read) and the auth prerequisite. It omits details such as empty-list behavior or pagination, but is otherwise complete enough for an agent to call it correctly.

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 tool has zero parameters, so the baseline is 4. The description does not need to explain parameter semantics and appropriately focuses on the result fields and auth requirement.

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 resource: coins watched by the caller's Toll key wallet on Robinhood Chain, and lists the returned fields. It stops short of explicitly contrasting with siblings like watch_coin and unwatch_coin, so an agent must infer this is the read/list counterpart.

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 by the phrase 'The coins your Toll key's wallet watches', and the prerequisite 'Needs a Toll key' is stated. However, there is no explicit when-to-use guidance or named alternative such as watch_coin for adding a watch.

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