list_admin_teams

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

With no annotations provided, the description carries the full behavioral burden. It helpfully discloses that the tool is self-hosted and admin-only, and 'List' implies a read-only operation. However, it does not explain pagination behavior, whether 'every team' is actually paginated, or any return/rate-limit characteristics.

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 short sentence with no wasted words, and the main purpose is front-loaded. It is appropriately sized for a brief list tool, though its terseness contributes to other gaps rather than serving as a model of balanced conciseness.

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 five-parameter list tool with no annotations and no output schema, the description is too sparse. It provides the admin/self-hosted context but omits pagination, search, ordering, sorting, and return-value expectations, leaving the agent under-equipped to invoke it confidently.

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 schema has five parameters (page, search, orderBy, pageSize, sortDescending) with 0% description coverage. The tool description mentions none of them, so it does not compensate for the completely undocumented parameters. An agent must infer all filtering, sorting, and pagination semantics from parameter names alone.

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 every team'. It also adds the scoping condition '(self-hosted admin only)', which helps identify the operation. However, it does not distinguish this from the very similar sibling tools list_teams and get_my_teams, so it falls short of a 5.

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 phrase '(self-hosted admin only)' gives a clear usage condition by restricting the tool to self-hosted admin contexts. But it does not explicitly say when to use this instead of list_teams or get_my_teams, nor does it explain exclusions beyond the admin/self-hosted constraint.

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