Run read-only Query on the monday.com API

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds that mutations are rejected with an error before the request is sent, which is valuable behavioral context beyond the annotations.

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?

Three sentences, each adding unique value: purpose, constraint, prerequisite. No unnecessary words.

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 general GraphQL query tool, the description covers purpose, constraints, and prerequisites. There is no output schema, but return values are not expected to be detailed. Missing mention of error handling beyond mutation rejection, but overall adequate.

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% with descriptions for both parameters. The tool description does not add additional meaning beyond the schema. The schema's description of 'query' mentions 'query/mutation' which slightly contradicts the tool's read-only claim, but this is minor.

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 'Execute read-only GraphQL queries against the monday.com API', specifying the verb (execute), resource (GraphQL queries), and constraint (read-only). It distinguishes from sibling tools that perform mutations or other operations.

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 advises using get_graphql_schema and get_type_details tools first, providing clear context. It explicitly states that mutations are rejected, helping the agent know when not to use this tool. However, it does not list specific alternative tools for similar read operations.

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