batch_get_node_properties

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

Consistent with readOnlyHint, describes return structure including errors, which adds value beyond annotations. No mention of limitations or auth needs, but acceptable for a read operation.

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 sentences, front-loaded with purpose and key usage note, no redundant information.

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?

Covers return structure, error handling, and changedOnly behavior. Without output schema, description adequately explains what to expect. Missing max batch size but not critical.

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?

Adds context for changedOnly (individual toggles) and explains return schema structure, supplementing the already complete schema descriptions.

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 clearly it gets properties from multiple nodes and positions itself as preferred over chained get_node_properties calls, distinguishing it from the single-node sibling.

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 says it's preferred over chained calls, guiding when to use. Mentions per-node changedOnly behavior but doesn't specify when not to use (e.g., for a single node).

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