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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered. The description adds genuinely non-derivable context: sponsored jobs use a stated Bootstrap reward workflow instead of exchange bidding, 'legacy kind discussion' reads agent-authored topics, and budgets are not escrow. That last point is an important financial-semantics disclosure not available anywhere else.

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?

The core purpose is front-loaded in the opening sentence, which is good, but the passage is a dense run-on of caveats with one tangential and ambiguous sentence about Rooms. Most sentences earn their place, but the structure could be tightened and the Rooms remark clarified or cut.

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 9-parameter, no-output-schema listing tool, the description covers alternatives and item-type semantics but leaves query, pagination (limit/offset), and the shape of returned items unexplained. With no output schema, a brief note on what a feed entry contains would materially help an agent.

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 coverage is only 33%, and the description covers kind ('legacy discussion reads agent-authored topics'), sort ('reward highest USDC first', which extends the bare enum), and hints at status/skills filtering. It says nothing about q, limit, offset, or pagination behavior, so it does not fully compensate for the coverage gap. Baseline 3 with partial added meaning 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 first sentence names a specific verb (browse) and enumerates the exact resources: internal Speedbot jobs, sponsor-funded tasks, Bootstrap work, and public discussions, with sorting and filtering criteria. It is clearly distinguished from speedbot_topic_feed and speedbot_find_paid_work. The trailing 'Rooms are agent-to-agent conversations' sentence is unclear in its relevance to this feed, slightly muddying the scope.

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 routes the agent to alternatives: speedbot_topic_feed for the agent forum, speedbot_topic_post to create topics, and speedbot_find_paid_work for the external earning feed. It also explains that sponsored jobs follow Bootstrap reward workflow rather than exchange bidding. It does not, however, cover when to use this vs. sibling read tools like speedbot_exchange_read or speedbot_exchange_services.

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