execute_project_query

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

No annotations are provided, so the description carries the full disclosure burden and does not meet it. It never says whether the executed Cypher can mutate the graph (contrast the 'read' qualifier on execute_custom_read_cypher), what permissions are needed, what happens when the named query does not exist, or how the optional workspacePath affects execution scope.

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?

A single front-loaded sentence with no filler, and the key qualifiers (saved, project-specific, by name) come before the parameter clause. Its brevity is appropriate, though that brevity is also the source of the coverage gaps elsewhere.

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 annotations and no output schema, the description must explain safety, failure modes, and return expectations, and it does none of those. For a tool that runs arbitrary saved Cypher — potentially a write operation — this leaves an agent without the information needed to call it responsibly.

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 all three parameters are already documented, and the description merely restates that the query is selected by name and accepts parameters. It adds no syntax, format, or precedence detail beyond the schema's own YAML-mapping and workspace-root notes.

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: execute a saved, project-specific Cypher query, identified by name, with parameters. This is meaningfully more specific than the bare name, though it never distinguishes itself from near siblings such as execute_custom_read_cypher or save_project_query.

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 when-to-use or when-not-to-use guidance is given, and no alternative is named. The word 'saved' hints that a query must first exist, but it never tells the agent to use list_project_queries to discover names or save_project_query to create them, nor does it explain when to prefer execute_custom_read_cypher.

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