List API Keys

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

No annotations are provided, so the description carries full burden. It discloses authentication requirements (scoped vs. unscoped routes) and return fields, but does not explicitly state whether the operation is read-only or idempotent. While it adds useful context, the lack of a mutation disclaimer creates a gap.

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 uses markdown headings and bullet points for clear structure. It front-loads the purpose and then adds necessary details in a compact form. Every sentence serves a purpose, resulting in an efficient, well-organized text.

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 parameters and no output schema, the description covers purpose, authentication, return fields, and usage contexts. It is mostly complete but lacks mention of potential errors or rate limits. Still, it provides sufficient information for a simple list tool.

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?

The input schema has zero parameters, so schema description coverage is trivially 100%. Per guidelines, 0 parameters yields a baseline of 4. The description adds no parameter info because none exist, so it meets the baseline adequately.

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 it 'List API keys for the configured RawTree project', using a specific verb and resource. It distinguishes itself from sibling tools like create-api-key and delete-api-key, both named in the text.

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 states 'NOT for: Creating or revoking credentials' and lists concrete when-to-use scenarios: checking existing keys, obtaining key IDs before revocation, and auditing permissions. This provides clear guidance for agent decision-making.

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