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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds real content beyond them: it discloses that the payload spans owned studios, join requests and invite links, and both confirmed and pending work relationships — useful shape-of-data context.

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-loaded with the primary resource and ending with the actionable downstream pointer. It is dense (em-dash clauses, mixed ownership/directionality) but every clause carries information; slight re-reading is needed to parse 'studios where the human works'.

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?

There is no output schema, so the description must carry the return-value burden, and it does: it enumerates the returned groups and the confirmed/waiting distinction. Minor gaps remain — no sense of ordering, volume, or what an empty result means — but an agent could invoke this correctly.

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?

The tool takes zero parameters, so the baseline is 4. The mention of member_id is a returned field, not an input, and the description correctly does not invent parameter semantics for a no-arg call.

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 precisely — the human's studios, their teams, join requests, invite links, plus studios where the human works (confirmed or waiting). That enumerates the returned entity set well enough to separate it from queries like profile_card or project_status, though the verb is elided into a noun phrase rather than stated as 'returns/lists'.

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?

There is one concrete routing hint: 'member_id for edit_company_team', which tells the agent this is the source of the identifier the edit tool needs. Beyond that the when-to-use context is only implied (call it to see team/studio membership state); there are no explicit exclusions or alternatives named.

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