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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description correctly focuses on behavior they cannot express: the data is read live from the mirror node (freshness, no caching) and results are ordered most-recent-first. It doesn't state failure modes or latency, but adds meaningful context beyond the annotations.

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 sentence with the resource, scope, ordering, and data source all front-loaded; every clause earns its place and there is no filler.

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-parameter, no-output-schema list tool, the description covers what is fetched, what counts as a match, ordering, and the data source. The only mild gap is that the shape of each returned call record is unspecified.

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% for the single 'limit' parameter, and the description adds nothing about it. Baseline 3 applies when the schema fully documents parameters.

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 ('list') and a precisely scoped resource: successful calls touching the Voicescape Tips contract at a named address, explicitly including tips and marketplace purchases. It is easily distinguished in behavior from verify_tip by the 'latest ... most recent first' framing, though it never names a sibling to contrast against.

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 implies its use case (fetching a recent-activity feed of the Tips contract) but gives no explicit when-to-use or when-not-to-use guidance and no pointer to alternatives such as verify_tip for a single tip. Usage is left to inference from the purpose statement.

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