List Teams

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds valuable context: it returns a cursor-based paginated response with a data array and meta.next_cursor, and confirms ordering. This goes beyond the structured annotations without contradicting them.

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?

A single sentence that efficiently conveys the REST method, path, purpose, and response format. No redundant content or unnecessary filler.

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 list with 3 optional parameters and no output schema, the description adequately covers purpose, filtering, ordering, and pagination format. It does not mention error cases or defaults, but those are not critical given the schema and simplicity.

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?

The schema covers 100% of parameters with detailed descriptions. The description only says 'matching the given parameters' and 'ordered', which does not add meaning beyond the schema. Baseline 3 applies as the schema does the heavy lifting.

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 clearly states 'List teams matching the given parameters, ordered' with the endpoint 'GET /api/teams'. It distinctly identifies a batch-list operation, differentiated from siblings like gorgias_get_team (single team) and gorgias_create_team.

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?

The context is clear that this tool lists teams, implying use when retrieving multiple teams or applying filters. It does not explicitly mention alternatives, but the verb and resource make the use case obvious, and there are no exclusions or misleading statements.

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