rca_auth_generate_token

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

Discloses that the key does not expire, cannot be recovered later, and that roles are for audit only. These go beyond the annotations (readOnlyHint=false, etc.) and provide necessary behavioral context.

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 description is well-structured with a clear lead sentence, usage instructions, plan details, and param breakdown. It is slightly verbose but earns its length with useful 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?

Covers all aspects: purpose, usage, parameter details, return value (JSON with api_key), plan limitations, and security notes. The output schema is referenced, so return format is clear.

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?

Despite 0% schema description coverage, the description explains each parameter's purpose: roles are audit-only metadata, key_id is ignored, key_label is optional. This adds meaning beyond the raw schema.

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?

The description clearly states 'Generate a new API key for authenticating all other tools' and specifies it issues the Free plan. This distinguishes it from sibling auth tools like rotate and revoke.

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?

Explicitly says 'Call this FIRST before using any other RCA-MCP tool' and provides instructions on storing the key and passing it as the 'token' field. Also clarifies that paid plans are handled separately.

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