batch_get_properties

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

Without annotations, the description discloses that this is a read operation on live nodes and, importantly, that missing nodes are reported inline instead of failing, which is critical for error handling. It does not describe the response format or permissions, but covers the most essential behavioral nuance.

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 dense sentence conveying the operation, the batching benefit, and a key edge case, with no redundant words. It is perfectly sized and front-loaded.

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 description covers the core behavior and the missing-node edge case, but with no output schema and no parameter detail, the agent may not know the expected request/response structure. It is adequate for a simple batch read but leaves notable gaps for a tool with a nested parameter schema.

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 coverage is 0%, and the description fails to explain the structure of the nodes parameter: that each item requires node_path and optionally a list of properties to fetch. The agent cannot infer the request format or the meaning of the 'properties' field from the description alone.

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 tool reads properties from multiple live nodes in a single round trip, and explicitly calls out the missing-node behavior, distinguishing it from sibling write tools like batch_set_property and the singular get_node_properties.

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?

It provides clear context for when to use this tool: when you need to read properties from several nodes at once and want to minimize round trips. However, it does not explicitly mention alternatives like get_node_properties for single-node reads or state exclusions, but the batching benefit is implied.

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