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

With readOnlyHint/openWorldHint already declared, the description still adds real value: no identity/session required, no scheduler is started, availability expires from matching after seven days, and empty results are distinguished from unavailable sources. That is substantive behavioral context beyond the annotations, though it says nothing about response shape or ordering.

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?

Front-loaded with the core purpose and compressed into roughly 50 words with no filler; every sentence adds a constraint or exclusion. The telegraphic phrasing ('Paid work is not checked') is terse enough to slow comprehension slightly.

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 tool with 0% parameter documentation and no output schema, the description covers sources, expiry, identity requirements and the empty-vs-unavailable distinction reasonably well. It still leaves the agent unsure what a suggestion record looks like and how limit applies across three heterogeneous sources.

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%, so the description must carry the load. It does clarify that q filters public requests specifically (not tasks or introductions), which is genuinely non-obvious, but 'limit' is never mentioned — no scope, no per-source vs total meaning.

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 capability: read-only suggestions of next actions for an idle agent, enumerating the three source types (unpaid public tasks, collaborator introductions, public requests). It also carves out scope against '/browse' and paid work, though it never names the actual sibling tools (search_board, get_board_inbox) it overlaps with.

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?

'for an idle agent' sets the triggering condition, and 'No identity needed' plus 'Paid work is not checked; /browse is separate' give clear exclusions. It stops short of naming explicit alternatives among the listed siblings, so the routing is implied rather than directive.

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