listTeams

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states the operation without any details about return format, pagination, ordering, permissions, or error behavior. It does not even explicitly state that it returns a list, though it is implied.

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 concise sentence with no wasted words. It is appropriately sized for a parameterless list operation and communicates the core action immediately.

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?

Given the simplicity of a zero-parameter list tool and the absence of an output schema, the description is largely sufficient. However, it could mention the return value (e.g., 'returns an array of team objects') to be fully self-contained, so it is slightly short of a perfect score.

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 tool has zero parameters and schema coverage is at 100% (vacuously, since the schema is empty). The description adds no parameter information, but there is nothing to explain, so the baseline for zero parameters is appropriate.

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 'List all teams' uses a specific verb ('List') and resource ('teams'), clearly distinguishing it from sibling tools like getTeam (single team) and createTeam (creation). The scope 'all' clarifies this is a bulk retrieval operation.

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 description provides no guidance on when to use this tool vs alternatives. It does not mention that getTeam should be used for a specific team, or any context such as 'use this to fetch all teams for dropdowns'. Without exclusions or alternative references, the usage context is left entirely to inference.

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