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

No annotations are provided, so the description carries the full behavioral disclosure burden. It explicitly warns that the raw key is returned exactly once, is never recoverable, and can only be revoked—essential behavioral information for a secret-generating operation.

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?

Two tightly written sentences deliver the core action, prerequisite, and the critical one-time-secret warning without filler. Information is front-loaded and every clause earns its place.

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?

Given no output schema and no annotations, the description covers the most important runtime behavior: the one-time raw key, admin requirement, and role binding. It stops short of explaining error cases or the full response shape, but those are secondary to safe invocation.

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 60%, leaving label and mailbox_label undocumented. The description adds useful context for role binding and admin auth, but it does not explain the required label or mailbox_label parameters, so the agent still has to guess at their meaning.

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?

Description uses a specific verb and resource: 'Create' an 'access_key'. It adds distinguishing traits—scoped, revocable, bound to a role, and one-time raw key—that separate it from list_access_keys, update_access_key, and revoke_access_key.

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?

States a clear precondition: requires an admin owner_key. This gives practical context for when the tool is appropriate, though it does not explicitly mention alternatives such as update_access_key or revoke_access_key.

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