api_keys

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

With no annotations, the description must disclose behavioral traits. It only says 'query' implying read-only, but does not mention pagination behavior, return format, or any side effects. The example shows pagination variables but does not explain how they affect results.

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 a single dense paragraph with a long example. It is front-loaded with the purpose, but the variable listing and truncated example make it less concise and harder to parse. Some structure (e.g., bullet list of variables) would improve readability.

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 14 parameters, no annotations, and no output schema, the description is incomplete. It does not explain what the tool returns, how to interpret the response, or how to use the parameters beyond a partial example. This is insufficient for an agent to use the tool 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?

The schema descriptions are minimal ('GraphQL: String'), but the tool description lists all variable names and provides an example with structural hints (e.g., filter object containing customers, ids, name, pods, roles, users). This adds meaning beyond the schema by showing how parameters interrelate, though the example is truncated.

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 'query apiKeys' which identifies the verb and resource, distinguishing it from sibling tools like create_api_key and delete_api_key. However, it does not explicitly describe the returned data or scope (e.g., list vs. search), so it is not a full 5.

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?

No usage guidance is provided. The description does not mention when to use this tool versus alternatives like create_api_key or delete_api_key, nor does it mention any prerequisites or scenarios. This is a significant gap for a query tool.

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