execute_graphql

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

No annotations are provided, so the description bears full responsibility for behavior disclosure. It notes that mutations can be executed, implying side effects, but does not warn about destructiveness, authentication requirements, rate limits, or error behavior. For a tool that can run arbitrary mutations, this is a significant omission.

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?

Two sentences with no filler: the action is front-loaded, and the usage routing condition follows directly. Every clause earns its place.

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 and a high-complexity tool that accepts raw GraphQL, the description should clarify the response format and caution about side effects. It only covers purpose and usage, leaving invocation semantics like response handling and safety incomplete.

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?

Input schema covers 100% of parameters with descriptions, so baseline 3 applies. The tool description itself adds no parameter meaning beyond the schema, but the schema already documents each field's purpose 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?

States a specific verb ('Execute') and resource ('any GraphQL query or mutation against the API'), and distinguishes itself from siblings by positioning itself as the generic fallback when no specific tool exists. The behavior is immediately clear and unambiguous.

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 'Use this when no specific tool exists for your operation,' which is a clear positive condition and implies the exclusion when a specific tool is available. It doesn't name the specific sibling tools, but the condition is sufficient for routing an agent to look for more targeted alternatives.

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