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

Annotations already carry the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds genuinely non-redundant context: the list is public and readable by users who have not joined the event, and each row carries the team's public profile plus `open_roles`. It does not mention pagination or ordering, so not a full 5.

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 scope, then the sibling contrast, then follow-ups — a clean progression. Slightly longer than strictly necessary and the backtick-heavy styling adds a little noise, but every sentence carries distinct information.

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?

With no output schema, the description partially compensates by saying each row contains the team's public profile and its `open_roles`, which tells the agent what to expect back. Read access rules and follow-up tools are covered; return ordering and pagination semantics are the only real gap.

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 `page`, `search`, `page_size` and `event_slug` are already documented with defaults, bounds and max length. The description adds nothing param-specific, which is the correct baseline when the schema does the work.

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 and resource ('Browse the teams of one event that are advertising open positions') and pins down scope as the public find-a-team list. It explicitly names the sibling `team_open_roles` and contrasts direction, so an agent can distinguish the two without opening a schema.

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?

Gives the caller profile explicitly ('the tool for a person looking for a team'), states when the alternative applies ('team_open_roles ... lists open positions the caller already has access to'), and routes to concrete next steps (`team_request_join`, `event_join_as_free_agent`). Nothing is left to inference.

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