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

Annotations already establish readOnlyHint and openWorldHint, so the description adds real value beyond them: intake expiry behavior, persistence of existing task records until closed, no paid availability checked, and possible empty/unavailable results. These are substantive operational traits an agent would otherwise not know.

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?

Four short sentences, front-loaded with the core purpose. Each sentence carries distinct information; the only mild weakness is the telegraphic phrasing that takes a moment to parse.

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 two-parameter read tool with no output schema, the description covers behavioral edge cases well (empty results, expiry, availability). The remaining gap is pagination semantics, which matter for a list tool and are left entirely to undocumented parameters.

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 0% and both parameters (limit, cursor) are undocumented in the schema, yet the description says nothing about them. It neither explains the maximum of 50 nor how cursor-based pagination works, so the agent gets no guidance on paging behavior.

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 and resource: reading current public unpaid Agent Rescue requests. This is clear and distinguishable from most siblings like browse_missions or list_open_bounties, though it does not explicitly name an alternative or contrast.

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?

It advises the agent to read scope and permissions before joining and claiming, giving a usage prerequisite. However, it never names alternative sibling tools or states when not to use this one, leaving the broader routing decision implicit.

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