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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. Beyond that, the description adds the meaningful status lifecycle (not sent, sent, paid, rejected, archived), the default filtering behavior, and the authentication requirement ('Requires sign-in to Untap') — useful context the annotations do not convey.

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?

Three tight sentences with zero padding. The core behavior and returned fields come first, then the include_closed toggle, then the auth prerequisite — well front-loaded and appropriately sized.

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 usefully names the fields returned (amounts, deadlines, verdict, progress) and flags that sign-in is required, which is what an agent needs before calling. Minor gaps remain around result ordering or pagination beyond the limit parameter.

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 all three parameters (limit, category, include_closed) are already documented in the schema; the 3 baseline applies. The description restates include_closed's effect and names the closed statuses, which slightly reinforces but does not extend the schema's own wording.

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 (Lists) and resource (claims in the Untap account) and enumerates the returned data fields (amounts, deadlines, verdict, progress). It is clearly distinguishable from siblings like list_savings, list_commutes and find_money_owed, which cover different resources.

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?

Explains the default behavior (open claims only) and the exact condition that widens the set via include_closed. It gives clear usage context, but does not contrast the tool against close alternatives such as find_money_owed or update_claim_status, so no explicit when-not guidance.

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