list-teams

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

The description mentions pagination as a behavioral trait, but with no annotations provided, it fails to disclose other important aspects such as whether the operation is read-only, result limits, or return structure. This is minimal disclosure for a list tool.

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 highly concise with a single sentence that conveys the core purpose. It is front-loaded with the action and resource. However, it could be slightly improved by adding a brief note on usage context or exclusions.

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 tool's simplicity and the schema covering all parameters, the description provides basic completeness for listing teams. However, it lacks guidance on when to use this vs other list tools and does not mention behavioral traits like idempotency or rate limits, making it adequately complete but not fully comprehensive.

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 coverage is 100% with well-documented parameters including descriptions, defaults, and enums. The description adds context about 'search filtering and pagination' but does not provide additional meaning beyond what the schema already offers. Baseline score of 3 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 clearly states the action 'List Datadog teams' and specifies optional search filtering and pagination. It distinguishes the tool from sibling tools like create-team, get-team, update-team, and delete-team, which have different purposes.

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 explains what the tool does ('List Datadog teams with optional search filtering and pagination') but does not provide explicit guidance on when to use it versus alternatives, such as when to use get-team for a single team or when pagination is needed.

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