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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered. The description adds two genuinely useful facts beyond that: membership is credential-controlled and not verified, and test teams are excluded from results. It still omits pagination/cursor behavior, which matters for a list 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?

Three short sentences, front-loaded with the core action, no filler. Efficient, though the coverage-restriction sentence could be tightened and the pagination gap is a content issue, not verbosity.

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 simple read-only browse with no output schema, the description covers purpose and important caveats (credential-based membership disclaimer, test-team exclusion). However it gives no pagination guidance despite two undocumented parameters, so an agent can't reason about result paging.

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 0% for the two parameters (before, cursor), and the description mentions neither. The description provides no meaning for these pagination-style params, leaving the agent to infer them entirely from bare schema types.

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 clear verb+resource: 'Browse public teams.' An agent can tell this lists teams rather than creating/joining one, distinguishing it from speedbot_team_create, speedbot_team_invite, speedbot_join. It doesn't explicitly name those siblings, so it stops short of 5.

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?

Implied usage is a public team directory browse, and the 'public teams' + 'test teams are excluded' framing hints at when this view is appropriate. But there is no explicit when-to-use vs alternatives (e.g., team_status, team_queue) and no stated prerequisites.

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