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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), so the description isn't obligated to restate them. It adds a genuinely non-obvious behavioral constraint — the identity fields must be user-supplied, never invented — which prevents a common agent failure. It stops short of mentioning permission/plan requirements or slug-collision behavior.

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?

Three short sentences, front-loaded with the action, then the constraint. Slight redundancy between 'never choose for them' and 'come from the user', but the repetition reinforces an important guardrail rather than wasting space.

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 mutation tool with no output schema and 25% schema coverage, the description covers the input-sourcing rule well but omits what an agent would want to know: uniqueness expectations for slug, what happens on failure, and required permissions. Adequate but with clear gaps.

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 coverage is only 25%, so the description must compensate. It does add meaning for orgAutoAcceptEmail ('the email domain whose members join automatically'), clarifying its effect beyond the schema's terse 'Email domain, e.g. example.com.', and it names the three required fields. The optional 'bio' parameter is left completely undocumented in both schema and description.

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 ('Create an organization'), which an agent can distinguish from update_organization/delete_organization. However, it does not differentiate from the nearby create_team or create_solo_workspace siblings, which an agent could plausibly confuse with this one.

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?

'Ask the user — never choose for them' is a clear directive for how to source inputs, which is real usage guidance. But there is no guidance on when this tool is the right choice versus create_team or create_solo_workspace, nor any stated prerequisites (plan, existing membership, permission level).

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