get_entity_context_batch

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

With no annotations, the description carries the full behavioral burden. It says 'without changing them', which usefully signals non-mutation, and 'bounded' hints at resource limits, but it omits pagination behavior, error handling, permissions, and the meaning of timeout/max_bytes.

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 front-loaded sentence with no wasted words. Its brevity is efficient, though it contributes to the under-specification captured in other dimensions.

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 seven-parameter batch-read tool with no annotations and 0% schema description coverage, the description is too thin. Even though an output schema exists, an agent lacks enough context to understand required inputs, optional controls, or when to choose this tool over siblings.

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% for seven parameters. The description only loosely gestures at entity_keys via 'observed IDs', view via 'source or instance', and max_bytes/timeout_ms via 'bounded', leaving run_dir, cursor, fields, and the rest undocumented in both schema and description.

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 states a read operation over 'source or instance facts' for 'observed IDs', but the resource type is abstract and it does not distinguish this tool from siblings like query_source_entities or get_evidence_node. The verb is clear, but the scope remains vague.

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 no explicit when-to-use guidance, no exclusions, and no named alternatives. The only contextual clue is 'for observed IDs', which is not enough to route an agent among the many sibling tools.

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