nerdgraph_query

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal information. It implies a read/write operation ('Execute') without specifying permissions, rate limits, or response behavior. The agent must infer details from the tool name and context, which is insufficient for safe use.

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, efficient sentence with zero waste—every word contributes to conveying the tool's purpose. It is appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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 the tool's complexity (executing arbitrary GraphQL queries) and lack of annotations, the description is incomplete. However, the presence of an output schema mitigates some gaps by defining return values. The description should ideally include more about authentication, error handling, or query constraints to be fully adequate.

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 0%, so the description must compensate but does not add meaning beyond the schema. It mentions 'custom NerdGraph GraphQL query' which hints at the 'query' parameter's purpose, but provides no details on syntax, format, or the 'variables' parameter. Baseline 3 is appropriate as the schema defines parameters clearly despite lack of descriptions.

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 the action ('Execute') and resource ('custom NerdGraph GraphQL query'), making the purpose immediately understandable. It distinguishes itself from sibling tools like 'query_nrql' by specifying GraphQL rather than NRQL queries, though it doesn't explicitly contrast with all siblings.

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?

The description provides no guidance on when to use this tool versus alternatives like 'query_nrql' or other data retrieval tools in the sibling list. It lacks context about appropriate use cases, prerequisites, or exclusions, leaving the agent with minimal direction.

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