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

Annotations already declare readOnly, idempotent and non-destructive. The description adds real context beyond them: the read is bounded and chunked, continuation is driven by nextOffset plus sha256, recipe bytes are untrusted and do not authorize execution, and scope/retention authorization still applies.

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?

Four tight sentences with the core read action front-loaded, followed by continuation, trust and authorization caveats. Dense but each sentence carries a distinct constraint; no filler.

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 security and continuation semantics are well covered for a read-only tool whose annotations already handle the safety profile. However, with no output schema and 0% schema description coverage on 10 parameters, an agent still lacks documentation of the required identifiers and the distinction between checkId/eventId.

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% across 10 parameters, so the description must carry the load. It touches offset/limit implicitly ('bounded chunk', 'nextOffset'), plus sha256, pointer and source ('recipe'), but says nothing about projectId, environmentId, checkId or eventId, leaving roughly half the parameters unexplained.

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?

States a specific verb and resource: 'Read a bounded exact chunk of the retained batch recipe, optionally at a JSON Pointer.' The 'batch recipe' scoping differentiates it from the sibling firedrill_read_value, though the sibling is never named explicitly.

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?

Gives clear operational context: follow a batch reference, continue with nextOffset and sha256, and do not rerun work to recover source. It stops short of naming alternatives or stating when to prefer firedrill_read_value over this tool, so it lacks explicit exclusions.

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