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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description is not required to carry the safety profile. It does add that only the owner may act, that invite produces a link for a person or their AI agent, and that a username-restricted invite can only be accepted by that user — genuine context beyond the structured fields. It stops short of saying what `remove`/`revoke` actually destroy or whether they are reversible.

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 compact sentence with the actor and resource front-loaded and the action inventory following. The parenthetical about agent links is dense but earns its place; no 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-parameter, multi-action mutation tool with no output schema, the description covers purpose, actor, and the full action surface, and the schema fills in required fields and idempotency. Missing is any hint about what success returns or which parameters pair with which action beyond what the schema states.

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 explains each parameter and the enum documents the eight actions. The description only restates the action set with no additional syntax, format, or per-action parameter mapping, 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?

States a specific verb-and-resource pair ('manages their studio team') and enumerates the eight operations the single tool performs, so an agent can match it to a team-management request. It does not, however, distinguish itself from the sibling `company_team`, which clearly supplies the ids this tool consumes.

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 'owner manages their studio team' framing implies the actor and setting, but there is no explicit when-to-use/when-not guidance, no mention of calling `company_team` first to obtain `member_id`/`invite_id`, and no exclusions. Usage must be inferred from the action list.

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