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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real semantic context beyond them: origin is declared provenance and not proof of execution host, and below_level never treats N/A or unknown as zero. These clarify interpretation of results, which annotations do not.

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 dense sentences, front-loaded with the core purpose and then the field semantics an agent would most likely misread. No filler, and each sentence carries distinct information.

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?

No output schema exists, and the description says nothing about what a returned batch contains or how pagination results are shaped (only a cursor reset hint). For a 16-parameter filter tool the parameter-level guidance is thin, though annotations cover the safety profile and the tricky fields are addressed.

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 16 parameters, so the description must compensate. It explains the non-obvious ones — q is a literal name/ID prefix, dates bound submission time, origin's meaning, and the below_level dependency — but leaves limit, execution, repository, scenarioId, workflowRunId, configurationId and others undocumented, so coverage is partial rather than complete.

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 with scope: 'Filter retained batches in one project/environment.' The plural 'batches' plus the filter framing distinguishes it from the singular sibling firedrill_batch, but no sibling is named explicitly, so differentiation is implied rather than stated.

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 two conditional rules — 'below_level requires dimensionId/minimumLevel' and 'Change filters only after clearing cursor' — which tell the agent how to use certain filters correctly. However, there is no explicit when-to-use vs alternatives guidance (e.g., vs firedrill_batch, firedrill_runs, or firedrill_summary), so selection remains inferred.

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