get_nodes_info

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

The description implies a read operation ('Get full details'), but annotations set destructiveHint=true and readOnlyHint=false, indicating potential destructive behavior. This is a clear contradiction that severely misleads an agent about side effects.

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?

Two concise sentences that front-load the action and the key benefit over alternatives. 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?

Lacks explanation of return values (no output schema) and does not clarify 'full details'. The annotation contradiction further undermines completeness, preventing an agent from understanding the tool's full behavior.

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 single parameter 'nodeIds' is fully described in the schema with format examples. The description adds no extra meaning beyond the schema, and with 100% schema coverage, a baseline of 3 is appropriate.

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 the verb 'Get', the resource 'nodes', and explicitly differentiates from the sibling 'get_node' with the benefit of a single round-trip for multiple nodes.

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?

Explicitly recommends use over repeated calls to 'get_node' when multiple nodes are needed, providing clear usage context. No exclusion criteria are given.

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