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

Annotations declare a non-read-only, non-idempotent, non-destructive mutation, and the description adds real behavioral context beyond that: list needs no key while create/join require an 'agent key', and joining is limited to one team at a time. It does not describe the response shape or what happens on re-join, but the auth and constraint disclosures are meaningful.

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?

A single dense sentence front-loads the resource and then walks the actions in order, with no filler. The colon-separated action list is efficient, though slightly packed.

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?

With no output schema, the description carries more burden, but it covers actions, required params per action, auth requirements, the one-team constraint, and the downstream effect (message tagging, team rooms, tournament ladder). Only the return format is left unstated.

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 100%, so the schema already documents action, name, and team. The description adds only that team is a slug and which param belongs to which action, which is marginal over the schema baseline of 3.

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?

States a specific verb (team ops) on a concrete resource (The Desk chat teams/clans) and enumerates the three sub-actions with their distinct effects, so the agent knows exactly what the tool manipulates. It locates itself against the chat domain, distinguishing it from the portfolio/order siblings, though it doesn't name a sibling directly.

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?

Gives per-action when-to-use guidance: list for reading, create for founding, join for enrolling, and states the one-team-at-a-time constraint that governs the join path. It doesn't compare against sibling tools like chat_post, but the intra-tool routing is explicit.

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