batch_get_properties

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It only states 'Get multiple properties' and the prerequisite, failing to mention that the tool is read-only, how it handles errors (e.g., missing nodes or properties), performance implications, or return format. This is insufficient for a tool that batches requests.

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, concise sentence that conveys the core functionality and a prerequisite. It is front-loaded and efficient, though the emoji is not strictly necessary.

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 the tool's complexity (batch read with two parameters) and lack of output schema, the description omits crucial details such as the return format (e.g., a dictionary keyed by path), error handling for invalid paths or missing properties, and whether all properties must exist. This leaves an agent insufficiently informed for correct invocation and result interpretation.

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 100%, with both parameters ('paths' and 'properties') having clear descriptions in the schema. The description adds no additional meaning beyond what is already in the schema, so the baseline score 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 it gets multiple properties from multiple nodes in one call, with a specific verb 'Get' and resource 'properties from multiple nodes'. It effectively distinguishes from siblings like get_node_properties by emphasizing the batch aspect.

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?

The description only provides a prerequisite ('Game must be running') but offers no guidance on when to use this tool versus alternatives, such as when to use batch_get_properties over get_node_properties or get_game_node_properties. No explicit when-to-use or when-not-to-use advice is given.

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