evidence_batch_get

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

No annotations are provided, so the description must fully disclose behavior. The description is just a fragment and discloses nothing about side effects, whether it's read-only, pagination behavior, error conditions, or the return format. This is a complete failure to add behavioral context.

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?

While short, this is not conciseness but severe under-specification. The description contains zero informative content, only a phrase that mirrors the tool name. It has no structure, no front-loaded key information, and every word is wasted.

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 (8 params, no output schema, no annotations), the description is utterly inadequate. An agent cannot determine how to call this tool, what it returns, or why it differs from siblings. The description fails to cover even the basics required for correct invocation.

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 provides no parameter explanations whatsoever. With 8 parameters and 3 required (repository_id, target_commit, evidence_ids), the description adds zero meaning, not even hinting what these parameters do. The burden is entirely on the schema, which lacks 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?

The description 'evidence batch get' merely restates the tool name with no elaboration. It lacks a specific verb or resource description beyond the name itself, and provides no differentiation from siblings like evidence_get or node_batch_get. This is a tautology that gives an agent no clue about actual purpose.

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 no guidance about when to use this tool versus alternatives. No mention of use cases, prerequisites, exclusions, or when to prefer other tools like evidence_get or dict_read. An agent has no context for selecting this tool.

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