list_event_teams

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

The verb 'List' conveys a read-only intent, and 'for an event' conveys the scope, which is useful given no annotations are present. However, the description does not disclose pagination behavior implied by the continuation parameter or any other runtime traits.

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 a single focused sentence with no filler or redundant wording. It is concise and front-loads the main resource and scope, though it could trade some brevity for more practical detail.

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 two-parameter list operation with an output schema, the description is minimally adequate: an agent learns what to call and what event to pass. But without usage guidance, sibling differentiation, or pagination explanation, there are clear gaps for a tool with no annotations.

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 0%, so the description must compensate for parameter meaning. It clarifies that event_id refers to the event whose teams are listed, but it leaves continuation entirely unexplained beyond its type and default.

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 description states a specific verb ('List') and a specific resource ('group registration teams for an event'), so an agent can tell this is a listing operation scoped to an event. It does not explicitly contrast it with get_event_team or list_event_team_attendees, but the resource and scoping is clear enough.

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?

There is no guidance about when to use this tool instead of related siblings like get_event_team, create_event_team, or list_event_team_attendees. The description implies the event-scoped usage but provides no exclusions, prerequisites, or alternative conditions.

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