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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is largely carried by structured data. The description adds only the useful nuance that membership is studio-decided; it does not disclose what 'leave' actually destroys (membership record, role, visibility history) or what happens when a request is pending. For a destructive multi-action tool this leaves a real gap.

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 sentence front-loads the resource and enumerates the action set with no filler. Six distinct operations are conveyed in under thirty words, which is tight for the scope.

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 six parameters, six actions, and no output schema, the description should say more about outcomes — e.g. what state each action leaves the human in, whether request returns a pending status, or what errors to expect. It covers the action surface adequately but the return/result dimension is entirely absent.

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 every parameter including the per-action code, studio, company_id, and request_key already carries its own semantics in the schema. The description's action enumeration loosely mirrors the enum values but adds no syntax or format detail beyond it, so baseline 3 is appropriate.

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 a specific resource (a studio / the human's membership of it) and enumerates the six operations it performs: join by invite, request, leave, set role, hide, show. That maps cleanly onto the action enum, so an agent knows precisely what the tool does. It does not, however, tell the agent how this differs from adjacent tools like company_team, edit_company_team, or join_project, so it stops short of full sibling differentiation.

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 parenthetical '(the studio decides)' gives a genuine hint that a request may not be granted, which is useful context for choosing request over accept. Beyond that, there is no explicit 'use this when' framing and no pointer to company_team as the source of company_id, so an agent must infer how to obtain the identifiers each action needs.

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