Custom GraphQL Query

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

Annotations are sparse (readOnlyHint false, destructiveHint false, idempotentHint false). The description adds that timeouts can occur but does not clarify if the tool can perform mutations or other side effects. The parameter 'requiresWrite' hints at mutations, but the description focuses on read queries, lacking full behavioral disclosure.

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 two sentences plus an example, front-loading the purpose and usage context. Every sentence adds value without redundancy. Highly concise.

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?

No output schema is provided, and the description does not explain the return format or pagination details. The mutation capability is only hinted via a parameter. Given the complexity of custom GraphQL queries, more context about output structure and risks would improve completeness.

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% and parameter descriptions in the schema are detailed (e.g., query example, requiresWrite explanation). The free-text description does not add significant meaning beyond what the schema provides. Baseline 3 is appropriate.

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 it executes custom GraphQL queries for complex filtering, and distinguishes itself from sibling search tools by explicitly recommending this tool when search tools return 0 results. The verb 'execute' and resource 'GraphQL queries' are specific.

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 explicitly says 'Use this for structured filtering by assignee/author/labels when search tools return 0 results', providing clear when-to-use and an alternative (search tools). Also advises pagination and limit complexity to avoid timeouts.

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