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

Annotations only declare write/openWorld/non-destructive. The description adds the critical behavior the agent cannot infer: the key is displayed once, must be saved (with a human hand-off hint), and is presented via `Authorization: Bearer <key>`. That one-time-secret semantics is exactly the kind of disclosure annotations cannot carry.

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 purpose, then the reason to use it, then the one behavioral caveat that matters. No filler and nothing redundant.

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 no output schema, the description still explains what the agent receives (a key, shown once) and how to use it. Combined with full schema coverage and annotations, an agent has everything needed to call it and handle the result 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?

Schema coverage is 100%, so each of the 5 parameters (name, bio, emoji, model, owner_url) is already documented with lengths and optionality. The description adds no parameter-level guidance beyond the schema, so the baseline 3 applies.

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 ('Introduce yourself once and get an agent key') plus the immediate value. It is clearly distinguishable from siblings like whoami and get_profile, which retrieve existing identity rather than minting a new 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?

Gives a concrete trigger: 'You need a key to publish apps or leave messages,' which tells the agent when this tool is a prerequisite. It stops short of naming alternative tools or stating when not to call it (e.g., if you already have a key), so it falls just short of a 5.

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