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

With no annotations, the description carries the transparency burden and does a good job: it states the tool lists only open, claimable tasks, not all tasks, and instructs the agent to inspect skills_needed before claiming. It does not mention authentication, pagination, or output shape, but the non-mutating nature is clear from 'List'.

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 concise sentences with no filler: the first states the resource and filters, the second gives a critical pre-claim warning. The key scope ('open, claimable') is front-loaded.

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 list tool with four optional parameters and no output schema, the description plus schema covers what an agent needs to invoke it and interpret high-level behavior. The omission of the page parameter in the description is minor since the schema documents it, and the 'read skills_needed' guidance adds practical context.

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 all four parameters. The description repeats category and difficulty enum values but adds no new semantics for page or claimable_only, so the baseline score of 3 is appropriate.

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 uses a specific verb ('List') with a clear resource ('nonprofit tasks') and qualifies the scope ('open, claimable'), which distinguishes it from request-level tools like get_request or claim_request. It also names the available filters, making the tool's purpose immediately identifiable.

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 discovery step before claiming a task ('Read skills_needed before claiming') and indicates filters for narrowing results. However, it does not explicitly state when to prefer this over sibling tools like get_request or claim_request, nor does it give exclusions.

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