node_batch_get

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description states no effects, side effects, safety implications, or operational constraints. It is completely opaque.

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 extremely short, but this is not conciseness—it is under-specification. No useful information is front-loaded, and the single phrase adds no value. It fails to earn its place semantically.

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?

For a tool with 8 parameters, no output schema, and a large sibling set that includes similar batch operations, this description is grossly incomplete. It provides virtually nothing an agent needs to call the tool correctly.

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 description coverage is 0%, and the description adds no parameter meaning. With 8 parameters (including required ones like repository_id, target_commit, node_ids), an agent has no clue what these fields represent or how to populate them correctly.

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 'node batch get' simply restates the tool name, offering no verb-resource specificity or differentiation from sibling tools like 'get_nodes' or 'node_semantic_batch_upsert'. It is a tautology and gives an agent no understanding of what the tool actually does.

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?

There is zero guidance on when to use this tool versus alternatives. The description provides no context, no prerequisites, and no exclusions, leaving an agent to guess which of the many similar batch/get tools to pick.

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