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

The description adds significant behavioral context beyond the annotations: it explains the camelCase naming convention (differing from the REST API), describes the pagination flow (sending nextCursor back as cursor), and notes that q filters before paging. These are not in the annotations and are crucial for correct invocation. No contradiction with readOnlyHint, idempotentHint, or destructiveHint.

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 front-loaded with the purpose, then efficiently covers pagination, naming, and the caveat about membership. Each sentence adds value, and there is no fluff or redundancy. It is concise yet comprehensive.

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 list tool with no output schema, the description covers the return shape, pagination mechanism, filtering behavior, and explicitly points to a sibling for a related need. Nothing essential is missing for an agent to call it correctly.

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%, so the schema already documents all three parameters thoroughly. The description adds minimal new semantic meaning for parameters; it reinforces the q filter behavior and cursor usage, but these are largely restatements of the schema. Baseline 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 states a specific verb and resource: 'List the organization’s teams' and enumerates the fields returned. It also distinguishes itself from team.get by explicitly noting that team membership is not included, which separates it from a sibling tool.

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?

It clearly implies this is the tool for listing teams and directs users to team.get for membership details. However, it does not explicitly contrast with other list tools (e.g., member.list) or state when not to use it, so it lacks explicit exclusions beyond the team.get reference.

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