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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the constraining note 'Only returned tasks are current offers' which clarifies that the list is limited to current open offers, and enumerates the returned fields. This is useful context but doesn't go beyond what an agent might expect from a simple list operation; no pagination, limits, or data freshness details are given.

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 a single, front-loaded sentence that immediately states the action and scope, then lists the content fields. There is no fluff or redundancy, and each piece of information serves the agent's decision. It is highly concise and well-structured.

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 and no parameters, the description carries the full burden of explaining what the tool returns. It enumerates the exact fields returned and clarifies the 'current offers' constraint. For a simple list-all tool with no filters, this is complete—nothing an agent needs to interpret the result is missing.

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 per the rubric is 4. The description does not need to explain any parameter semantics because there are none; the schema is empty and coverage is 100%. No additional parameter context is possible or required.

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 states 'List every AB5D bounty that is currently open for claim' – a specific verb and resource, and enumerates the fields returned (reward, eligibility, claim route, submission route, protocol, acceptance command). This clearly distinguishes it from siblings like get_bounty (single item) and list_artist_otdh (different entity), so an agent can pick it without ambiguity.

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 this is the comprehensive list tool by saying 'List every...', but it offers no explicit when-to-use guidance, exclusions, or pointers to alternatives like get_bounty for specific items. The phrase 'Only returned tasks are current offers' adds a nuance about filtering, but it's not a full usage guideline. The agent must infer the selection logic from the description.

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