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

Goes well beyond the annotations by disclosing the authorization requirement and a concrete business invariant with its error outcome ('label can become an artist workspace only while it has one artist or none (409 otherwise)'). These are exactly the facts that determine whether a call will succeed, and they are not derivable from readOnlyHint/idempotentHint.

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 dense sentences with no filler: operation first, permission second, edge condition third. Every clause carries operationally relevant information.

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 two optional params, no output schema, and solid annotations, the description covers purpose, auth, and failure modes. It leaves minor gaps: what happens if neither parameter is supplied, and whether renaming is a no-op when the name is unchanged.

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 100%, so the baseline is 3; the description adds that the parameters are alternatives (rename vs. switch) rather than both required, and attaches the constraint to the 'type' transition. It slightly exceeds what the schema 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?

States a specific verb and resource ('Rename the organization (workspace)') plus the second operation ('switch it between artist and label'), and clarifies the credential-scoped meaning of 'organization'. This distinguishes it from create_organization, list_organizations, and rename_artist without needing the schema.

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?

Gives an explicit precondition ('Owners and admins only') and a conditional rule for each direction of the type switch, including the 409 failure case. It doesn't explicitly name sibling alternatives, but the resource scope makes the boundary obvious.

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