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

Annotations already declare readOnlyHint/idempotent/non-destructive, and the description usefully reinforces this with 'Reads never create work or spend' plus an explicit anonymous-vs-authenticated scope model — real value beyond the annotations. However, it never says which of the twelve operations require auth, what pagination or limits apply, or why a 'quote' operation lives on a read tool.

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 the auth/scope sentence is well placed. The twelve-item operation list is dense but unavoidable given the union schema. The closing sentence about composition priority and Weekly/Pro scores is tangential and the weakest use of space.

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 twelve-operation polymorphic tool with a large oneOf schema and no output schema, the auth-scoping sentence carries most of the weight and does describe what read/role return (private role, dependency results, next action). But the distinction between list vs mine, read vs role, blueprints vs blueprint, and quote vs rehire_quote is left entirely unexplained.

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 per-operation union, required fields, and agent_key guidance are already fully documented in structured data. The description's only parameter contribution is restating the operation enum values, which the schema already constrains via const. Baseline 3 applies.

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 opening verb+resource ('Find or resume outcome-based swarms') is stated, but 'outcome-based swarms' is undefined jargon and the twelve operations are dumped as a bare enumeration with no gloss on what any of them do. Nothing distinguishes it from read-flavored siblings such as speedbot_read, speedbot_request_read, or speedbot_product_read.

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?

'Find or resume' implies two contexts, and the sentence about anonymous previews vs authenticated members gives a real selection rule for the read/role path. But there is no guidance on when to use this versus speedbot_read or speedbot_action, and no indication of which operation to pick for which goal.

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