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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds valuable behavioral context by enumerating the specific output fields (status, clips, counts, links), which goes beyond the generic annotations. This merits a 4.

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 sentence that front-loads the action and lists key outputs in a compact manner. No unnecessary information or filler, earning a 5.

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 simple, read-only getter with an output schema and strong annotations, the description is complete. It clearly states the purpose and return contents, with no missing critical context. The tool's simplicity and structured data make this comprehensive without needing extra detail.

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 100%, with both parameters (batchId, workspaceId) fully described including UUID format and default behavior. The description adds no parameter-specific meaning, so the baseline of 3 is appropriate as the schema does the heavy lifting.

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 uses a specific verb 'Get' and names the resource 'BlitzReels clip batch', listing the exact outputs: status, generated clips, render counts, download links. This clearly distinguishes it from siblings like clips_create or clips_manage, which handle creation or broader management.

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?

The description implies usage after creating a batch (e.g., via clips_create) by stating it retrieves batch data. It gives clear context for when to use it, though it does not explicitly name alternatives or exclusions. Given the tool's name and sibling context, this is sufficient for a 4.

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