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

Annotations already declare a non-destructive, idempotent, closed-world mutation, so the safety bar is lower. The description adds real behavioral context beyond that: admin-only authorization, a plan-tier restriction for domains, and the critical 'Empty clears it' semantics for domain auto-join. It does not discuss what happens to unmentioned fields, which keeps it below a 5.

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 tightly packed sentence with the primary verbs front-loaded and the authorization caveat inline. No filler and nothing restated from the title.

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?

An output schema exists, so return values need not be explained, and all five parameters are fully documented in the schema. The description covers auth, plan restrictions, and clearing behavior; the only minor gap is that it does not surface the requirement to pass either team or team_id, which the anyOf constraint already enforces.

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 each parameter, including the empty-clears and team-plans-only notes for domains and the 1-60 character limit on title. The description only loosely maps its verbs to parameters ('by email domain', 'make it your default') without adding format or constraint detail beyond the schema, so the baseline 3 applies.

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 names the resource (team) and three concrete operations: rename, set domain-based auto-join, and set as default. An agent can distinguish this from update_team_member or create_team by the operations described, though no sibling is named explicitly.

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 states the precondition '(team admins only)' and notes 'Team plans only' for domains, which is genuine when-to-use guidance. However, it never routes the agent to alternatives such as update_team_member for membership changes or create_team when the team does not exist, so selection still requires inference.

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