advanced_query

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

No annotations are provided, and the description does not disclose side effects, safety (e.g., read-only vs. mutating), rate limits, or error behavior. For a tool that executes queries, this omission is significant for agent decision-making.

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 a single, concise sentence that front-loads the tool's purpose. No superfluous words or redundant information.

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?

Despite full schema coverage, the description lacks usage guidelines and behavioral transparency. For a tool with many siblings and no output schema, it should explain scope (e.g., supported queries, mutation status) to be practically complete.

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 description coverage is 100%, so baseline is 3. The description adds the term 'Cypher-like' to contextualize the query syntax, but provides no additional meaning beyond the schema definitions. The 'explain' and 'parameters' fields are adequately described in the schema.

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 specifies executing advanced Cypher-like graph queries with filtering, aggregation, and pattern matching. It identifies the resource (graph queries) and action (execute). However, it does not fully distinguish from siblings like aggregate_query or temporal_query, as 'advanced' and 'complex' are vague differentiators.

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?

No guidance on when to use this tool vs alternatives. The sibling list includes many query tools (e.g., aggregate_query, execute_saved_query), but the description provides no criteria for selection, such as when to choose advanced_query over simpler query tools.

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