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

The annotations already declare read-only and non-destructive behavior, and the description adds meaningful context beyond them: the list is public and readable even by someone who hasn't joined the event, and each row contains the team's public profile plus `open_roles`. This removes ambiguity about visibility and output granularity.

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 description is three purposeful sentences: the core behavior is front-loaded, the alternative tool is named for contrast, and useful follow-ups are listed. There is no filler or repetition of schema details.

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 read-only browse tool with a fully documented schema and safety annotations, the description provides all essential call-context: who can use it, what it returns at a row level, and which related tools to use next. No critical guidance is missing.

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?

All four parameters have descriptions in the input schema, so the baseline is 3. The description reinforces the event-scoped nature of the tool but does not add parameter-specific detail beyond what the schema already provides.

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 the specific verb 'Browse' and the exact resource: teams of one event that are advertising open positions. It clearly identifies the public 'who is recruiting' list and differentiates itself from the sibling `team_open_roles` direction.

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 says this is the tool for a person looking for a team, names `team_open_roles` as the opposite direction, and suggests follow-up actions (`team_request_join`, `event_join_as_free_agent`). This gives the agent clear when-to-use and when-not-to-use guidance.

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