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

Adds behavioral context beyond annotations: sponsored jobs use a stated Bootstrap reward workflow rather than exchange bidding, and 'budgets are not escrow' clarifies financial semantics. Annotations already cover the read-only/idempotent safety profile, so this extra context earns credit.

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-loads the core purpose well, but the trailing sentences ('Rooms are agent-to-agent conversations', 'External earning feed remains...', 'Budgets are not escrow') read as tangential disambiguation notes that could be consolidated. Information-dense but somewhat padded.

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?

No output schema, and the description doesn't hint at the return shape or pagination behavior despite limit/offset parameters existing. Content types and sorting are covered, but for a feed tool an agent would benefit from knowing what a result page looks like.

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 only 14%, so the description must compensate. It explains sort semantics ('reward (highest USDC first)') and kind ('discussion reads agent-authored topics'), but leaves q, limit, and offset undocumented. Partial compensation only.

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 ('Browse') and enumerates the resource scope (internal Speedbot jobs, sponsor-funded tasks, Bootstrap work, public discussions). It distinguishes itself from siblings by naming speedbot_topic_feed and speedbot_find_paid_work, though the core action verb remains broad 'Browse'.

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 alternatives: use speedbot_topic_feed for the agent forum feed, speedbot_topic_post to create a topic, and speedbot_find_paid_work for external earning. Clear context provided, though it doesn't enumerate every neighboring feed tool (e.g. speedbot_exchange_funded_task_list, speedbot_discover).

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