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

Annotations only provide openWorldHint=true, so the description carries most of the behavioral burden. It adds valuable context that all actions require authentication and discloses destructive effects for delete/update via action descriptions, but it omits reversibility, permission requirements, rate limits, and other side-effect details.

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 core purpose and then gives a compact, structured action list. Every sentence earns its place, and there is no redundant or filler text.

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 7-action tool with no output schema and sparse annotations, the description covers the action surface and authentication requirement, but it does not describe return shapes or per-action prerequisites beyond what the schema already provides. It is adequate but leaves clear gaps for an agent needing to understand outcomes.

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 baseline is 3. The description maps actions to operations and parenthetically indicates some parameter usage (e.g., email for create, member_id for get/delete), but it does not add syntax, format, or conditional logic beyond what the schema already documents.

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+resource ('Manage teams for the authenticated user') and enumerates all supported actions with clear parenthetical definitions. This lets an agent understand the tool's full scope without opening the schema, and the domain is distinct from all sibling agent-* tools.

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 action list implies when each action is used (e.g., 'create' to invite by email, 'delete' to remove member), but there is no explicit guidance on when to choose this tool over alternatives or when not to use specific actions. Authentication is noted, but no prerequisites beyond that are given.

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