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

Annotations only declare the operation is a non-idempotent, non-destructive write. The description adds critical behavior beyond that: the tool returns an API key, the key is shown only once, the user must store it securely, and the key is later supplied via an Authorization header or apiKey argument. These are non-obvious operational facts an agent cannot infer from annotations.

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 tightly packed sentences: purpose and return value first, then the when/when-not rule, then the operational warning about the key. No sentence is redundant and the most decision-relevant information is front-loaded.

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 three-required-parameter account-creation tool, the description covers purpose, routing logic, and the downstream consequence of the returned credential. An output schema exists, yet the description still flags the one-time key disclosure, which is the detail most likely to cause user harm if missed.

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 description coverage is 100%, so name, email, and password are already fully documented in the schema, including the 8-character minimum. The description restates the same three inputs but adds no format, constraint, or edge-case detail 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 ('Create a new KadiConnect account') and immediately names the key output artifact ('receive an API key (starts with kc_)'). This is clearly distinguishable from all siblings, which operate on cards, links, leads, and analytics rather than account creation.

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 use condition ('Use this only when the user wants a new account') and an explicit exclusion with the alternative ('if they already have an API key, use that instead'). The agent is told exactly when not to call this tool.

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