graphql_query

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

The readOnlyHint annotation already establishes this as a safe read operation. The description adds the fact that it executes 'raw GraphQL', which implies arbitrary query complexity, but it does not disclose rate limits, response size limitations, or how to obtain the GraphQL schema. This is adequate but not rich.

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?

A single sentence that is front-loaded with the key information. Every word earns its place, and there is no filler or redundancy.

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 an advanced tool with high flexibility, the description is extremely minimal. It does not guide the user on constructing queries, point to graphql_schema for the schema, or mention any constraints. While the output schema covers return values, the overall context for effective use is 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?

With 0% schema description coverage, the description should compensate by explaining parameters. It only mentions 'GraphQL query', which maps to query_string, but variables and operation_name are left entirely to the schema. No additional meaning is provided for these GraphQL conventions.

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 verb 'Execute' and the resource 'raw GraphQL query against Open Targets', distinguishing it from the many specific get_* tools and from graphql_batch_query. The 'ADVANCED' prefix helps emphasize it's a low-level interface.

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 'ADVANCED' label implies use for non-standard queries, but there is no explicit guidance on when to use this over the specialized endpoints or which alternatives exist. The description does not mention graphql_schema or other related tools.

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