get_nodes_info

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

No annotations present; the description lacks details on what 'detailed properties' entails, permissions needed, or rate limits, leaving behavioral assumptions unclear.

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?

Single sentence, no wasted words, efficiently communicates the core purpose.

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?

No output schema; description does not clarify what 'detailed properties' includes (e.g., all properties or a subset). For a simple tool this may suffice, but additional context would improve completeness.

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 has 1 parameter (nodeIds) with 100% description coverage ('Array of node IDs'), so baseline is 3. The description does not add further meaning beyond that.

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 'Get detailed properties of multiple nodes' clearly states the verb 'Get' and resource 'detailed properties of multiple nodes', distinguishing it from siblings like 'get_node_info' (singular) and 'get_selection'.

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 over alternatives, such as when to use get_node_info vs get_nodes_info, or any prerequisites.

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