queryNode

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

No annotations are provided, so the description must disclose behavioral traits. 'Query' implies a read-only operation, and 'its relationships' hints at relationship traversal, but there is no explicit mention of safety, side effects, or limits. The description adds minimal behavioral context beyond the verb itself.

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 sentence with no filler words, front-loading the verb and resource. It is highly concise, though it may be under-specified; conciseness itself is exemplary.

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?

The tool has no output schema, so the description should explain what the query returns. It only states 'Query a node and its relationships' without detailing return format, depth behavior, or how relationships are represented. With no annotations and no output schema, the description is incomplete for a tool with 4 parameters and relationship traversal.

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%, with all four parameters documented in the input schema. The description itself adds no parameter-specific meaning, but the schema already provides descriptions for id, depth, projectId, and includeNeighbors, so the description is not required to compensate.

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 uses the verb 'Query' and specifies the resource 'a node and its relationships,' clearly stating the tool's function. However, it does not explicitly distinguish from sibling tool 'searchNodes' or mention that it queries by ID, so it is clear but lacks sibling differentiation.

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 provides no guidance on when to use this tool versus alternatives such as 'searchNodes' or 'listProjects'. No context or exclusions are given, leaving the agent to infer usage from the name alone.

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