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

Beyond the annotations (readOnlyHint=false, destructiveHint=false) it discloses the critical behavior that the response carries a live credential in `token` and instructs not to repeat, log, or pass it to another tool. It also layers in auth-mode constraints and role requirements, which annotations cannot express.

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?

The purpose and the credential-handling warning are front-loaded, and nearly every sentence adds decision-relevant information (credential hygiene, type/auth matrix, role requirement, resource layout). It is long but dense; some of the auth matrix could be tightened into a list without loss.

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?

An output schema exists and the description still usefully flags the `token` field's sensitivity. Auth, role, resource-identification, and confirmation-before-calling requirements are all covered; the notable omission is gateway resource parameters.

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 reported as 0%, so the description carries the burden and largely does: it names organizationId, name, and type as required, and spells out the exact resource shapes for SUBGRAPH keys (graphId, variantName, subgraphName) and VARIANT keys (graphId, variantName). It never mentions `resources.gateways` / GatewayIdentifierInput, so gateway key resource wiring remains undocumented.

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?

"Create an API key for an organization" gives a specific verb plus resource, and the surrounding text makes clear it is the creation member of the GetApiKeys / RenameApiKey / DeleteApiKey family. An agent can select it without opening any 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?

It states exactly which key types each authentication mode permits (OAuth → OPERATOR/SCIM/GATEWAY; personal API key → SUBGRAPH/VARIANT; operator key → GATEWAY only; graph key → none; nothing → ROUTER) and who needs Org Admin. It also gives prescriptive guidance: pick the narrowest type and confirm type plus resources with the user before calling.

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