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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, but the description adds real value beyond them by enumerating the side effects it never performs (claiming, joining, starting agents, promising payment) and by documenting the cursor/hasMore pagination loop. It still does not describe result shape or ranking guarantees beyond the schema's field notes.

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 short sentences, front-loaded with purpose, followed by the boundary and pagination note. No filler or restated title.

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 read-only, no-required-param tool with a fully documented schema, the description covers purpose, boundaries and pagination, which is most of what an agent needs. It leaves the return shape unstated (no output schema), though nextCursor/hasMore are mentioned.

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 after, limit, skills and interests, including that skills/interests only re-rank and filter nothing. The description only reinforces the cursor-chaining convention, adding little beyond the schema, so the baseline 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?

States a specific verb and resource ('Recommend available volunteer tasks'), so the agent knows exactly what the tool produces. It does not explicitly name or contrast with the sibling room_join_* tools, so sibling differentiation is only implicit via the read-only disclaimer.

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?

Explicitly bounds when this tool applies: 'Read only; never claims, joins a room, starts an agent or promises payment,' which steers the agent away from the join/claim siblings. It also gives continuation guidance ('Continue using nextCursor as after when hasMore'), but states no positive precondition for when recommendations are wanted.

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