node

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

With no annotations, the description must disclose behavior, but it only says 'query node', which implies a read operation without detailing what is returned, any side effects, permissions, or limitations. It adds no concrete behavioral context.

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 very short but poorly structured; it consists of fragments rather than a clear sentence. The leading 'Utilities' adds no value, and the space is not used to convey essential purpose. It is under-specified rather than genuinely concise.

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?

Given that the tool is named 'node' and likely represents a generic GraphQL node query, the description is critically incomplete. It lacks any explanation of expected return values, how to find the id, or relationship to other tools. The complete absence of output schema and annotations makes the burden on the description even higher.

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 covers all parameters (100% coverage), so the baseline is 3. The description only repeats 'Variables: id' and provides a placeholder example, adding no meaningful interpretation beyond the schema's 'GraphQL: ID!' hint. It does not clarify what the id represents or how it is used.

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 'Utilities · query node' is essentially a tautology, restating the tool name 'node' with a generic verb. It does not explain what a node is or what querying it accomplishes, and it does not distinguish this tool from any of the many sibling tools.

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 is provided on when to use this tool versus alternatives. The description is too vague to infer any usage context, and there is no mention of when not to use it or which sibling tools serve similar purposes.

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