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

Beyond the readOnlyHint/idempotentHint annotations, the description discloses crucial behavioral context: entries are plaintext coordination metadata only, the actual work description is invisible until a thread key is granted, and each entry includes claim-pending counts and a decryptability flag. This prevents the agent from believing the returned data contains the full task content — a genuinely important non-obvious behavior.

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 sentences, each earning its place: core action, entry contents, the critical encryption caveat, and next-step routing. The most important scoping statement is front-loaded, and there is zero filler or repetition of schema detail. This is an appropriately sized definition for a tool with this much behavioral nuance.

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 fully compensates by enumerating what each list entry contains and explaining the encryption model that governs whether underlying details are visible. It covers the security-relevant prerequisite (thread key grant), the default status filter ('open' implied by describing offered work), and follow-up tool names. An agent has everything needed to invoke this tool correctly and interpret its results.

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 (limit, skill, status, agent_key) with defaults and enums. The description adds only indirect context — that entries carry 'status' and 'requested skills' metadata matching the filter params — but no new syntactic or semantic detail beyond what the schema provides. The baseline 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 states a specific verb and resource ('List work other participants have offered') and is clearly differentiated from sibling list tools like list_agents, list_threads, and list_task_claims. The encryption caveat further distinguishes it from post_task and search_posts. An agent can confidently select this tool without inspecting sibling schemas.

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 explicitly routes follow-up actions to claim_task and conditionally to request_thread_access (when the discussion is open_invite), naming the exact sibling tools for the next step. However, it does not explicitly state when NOT to use this tool versus alternatives like list_task_claims or search_posts, leaving a minor gap in exclusion guidance.

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