graphql_query

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It does disclose the permission requirement for mutations and distinguishes read-only queries, which is useful. Still, it omits details about error behavior, response format, or side-effect consequences beyond the word 'mutations.'

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 entire description is a single concise sentence that front-loads the tool's purpose and adds a critical permission caveat. There is no filler, redundancy, or repetition of the schema.

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?

For a raw GraphQL tool with no annotations, no output schema, and undocumented parameters, this description is too sparse for safe invocation. It explains what the tool does and the permission gate for mutations, but leaves parameter semantics, usage context, and operational details unstated.

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%, and the description does not explain the three parameters: query, profile, and variables. The word 'GraphQL query' may imply what the query parameter holds, but profile and variables are completely undocumented, leaving a significant gap.

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 states a specific action and resource: 'Run a Survey Solutions GraphQL query.' It clearly identifies this as a GraphQL tool, which separates it from REST or OpenAPI siblings, though it does not explicitly compare against those alternatives.

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?

It provides clear context that read-only queries are generally allowed while mutations require raw_api permission and allowRawGraphqlMutations. However, it does not explicitly say when to prefer this tool over sibling tools like rest_request or openapi_operation, nor does it describe when not to use it.

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