integrations

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

No annotations are provided, so the description carries full responsibility for disclosing behavior. It only lists variables and an example, without stating that this is a read-only query, how pagination works, or what happens with the filter. The behavior is implied but never explicitly described.

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 includes a redundant 'Query Management ·' prefix and a variable list that largely duplicates the schema. The example JSON is valuable but verbose. It is not maximally concise, though the structure is clear: intro, variables, example.

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?

With no output schema and no annotations, an agent cannot determine what the tool returns. The description provides an example input but not the response shape, pagination details, or error behavior. For a complex query tool with five parameters, this is insufficient for confident invocation.

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?

The schema descriptions are generic GraphQL types, but the example variables add significant meaning by showing the concrete structure for integrationFilter and integrationOrder. This goes beyond the sparse schema and helps an agent understand how to construct valid inputs. However, individual parameter purposes are not described in words.

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 says 'query integrations,' which identifies the resource but not a specific verb like 'list' or 'fetch.' It is essentially a restatement of the tool name with 'query' prefixed, providing only vague purpose. The example variables imply it returns integrations based on filters, but that is not explicitly stated.

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?

There is no guidance on when to use this tool versus alternatives. The sibling 'integration' (singular) might be the single-item counterpart, but the description never mentions this distinction or any other usage context. No exclusions or alternatives are provided.

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