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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the bar is lower, yet the description adds real domain behavior: the document is 'bounded' and 'service-owned', recipe fields may be omitted and require reference-following, and completion state must not be conflated with assessment success. The explicit 'this read does not execute the recipe' reinforces readOnly with domain-specific meaning.

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?

Three sentences, each carrying distinct load: what is returned, how to chase omitted fields, and a semantic caveat. No filler, and the core purpose is front-loaded.

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?

There is no output schema, so the description usefully enumerates the returned contents, and the reference-following note covers the main downstream need. Gaps remain around error/not-found behavior and the meaning of the three identifier scopes.

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%, so all three required identifiers (projectId, environmentId, batchId) are documented nowhere. The description never mentions a parameter or explains the project/environment scoping that governs which batch is resolvable, so it fails to compensate for the coverage gap beyond self-evident naming.

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?

Specific verb 'Read' plus a precise resource ('the bounded service-owned batch document') and an enumeration of what it contains: execution counts, cancellation state, recipe metadata. It implicitly separates from the sibling list tool firedrill_batches (singular document) and names firedrill_batch_value for the follow-up case, though the list-vs-document contrast is never stated outright.

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?

Routes the agent to firedrill_batch_value when recipe fields are omitted, which is a concrete alternative-plus-condition. It also warns that 'completion is not assessment success', nudging consumers toward the assessment tools. It stops short of stating when not to use this tool (e.g., when the batch list or summary is wanted instead).

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