pm_list_teams

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

No annotations provided, description only gives HTTP method and optional filter. Lacks disclosure of authentication, pagination, rate limits, or response behavior. For a tool with no annotations, description is insufficient.

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?

Extremely concise single sentence, front-loaded with the HTTP method and endpoint. No unnecessary words.

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?

Despite having an output schema, description doesn't mention it returns a list of teams or any output details. Missing behavioral context like required permissions or default behavior without filter.

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 description coverage is 0%. Description mentions 'optional organization_id filter' but doesn't explain x_user_id parameter or provide any formatting details. Adds minimal value beyond schema names.

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?

Description clearly states it's a GET to /teams with optional organization_id filter, indicating retrieval of a list. It distinguishes from siblings like pm_get_team (single team) and pm_create_team (creation).

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?

Implies usage for listing teams, but no explicit guidance on when to use this vs alternatives like pm_get_team or filtering scenarios. No exclusions or prerequisites mentioned.

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