Run a GraphQL query against the Snapshot hub

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

Adds substantial behavior beyond annotations: only query operations are allowed, responses over 1 MB are refused, and results over 50k characters are truncated. Annotations already declare readOnly/openWorld, but the response-size and operation-type constraints are valuable context.

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?

Front-loaded with the core purpose, then constraints and schema reference in a compact paragraph. Every sentence earns its place by clarifying scope, limits, or safe usage.

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?

Complete for an open-ended GraphQL query tool with no output schema: it explains allowed operations, size limits, truncation behavior, pagination guidance, and points to the external schema reference. Nothing essential for correct invocation is missing.

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 coverage is 100%, so the query and variables parameters are already documented. The description adds meaningful usage semantics beyond the schema: use first/skip, select only needed fields, and keep responses within size limits.

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 and resource — runs GraphQL queries against the Snapshot hub API — and enumerates the domains it can query. It explicitly positions itself as the fallback for questions the fixed read tools do not cover, distinguishing it from sibling read tools.

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?

Gives explicit when-to-use guidance: for questions the fixed read tools do not cover, with concrete examples. It also gives when-not guidance by stating that mutations and subscriptions are rejected, and recommends pagination/field selection.

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