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

The description repeats the read-only nature implied by the 'readOnlyHint' annotation by including the HTTP GET method, but adds no additional behavioral context (e.g., rate limits, auth requirements, or side effects). Since annotations already cover readOnlyHint, the description contributes minimal extra value.

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 very concise—a single sentence plus an endpoint reference. It wastes no words, though a bit more structure (e.g., separating purpose from endpoint) could be beneficial. It is well front-loaded.

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 simple list operation with no output schema, the description is minimal but sufficient. It does not mention pagination, return fields, or behavior when no parameters are provided. Given the tool's simplicity, the description is adequate but not thorough.

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?

With 100% schema description coverage, the baseline is 3. The description offers no parameter explanations beyond what the schema already provides (limit, offset, organization). It does not clarify parameter usage or constraints further.

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 the tool's function: 'List teams in the organization(s).' It provides the specific API endpoint ('GET /teams'), making the purpose unambiguous. It appropriately distinguishes from sibling tools which list other entities like contacts or conversations.

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?

No guidance is given on when to use this tool versus alternatives, nor are there any prerequisites or exclusions mentioned. The description merely states what it does, leaving the agent to infer usage context.

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