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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so 'Read-only' restates structured data. The one piece of genuine new context is the 30-day lookback window, which an agent could not infer elsewhere; pagination behavior and result ordering go unmentioned.

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 short sentences, trigger-first, with no filler. 'Read-only' is the only expendable clause since annotations already cover it.

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?

Output schema exists, so return shape needn't be explained, and all three optional params are schema-documented. With the trigger and the 30-day scope stated, an agent has enough to call this correctly; only the hand-off to batch-detail tools is left implicit.

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% – q, per_page and batch_type all carry inline documentation with ranges and enum meanings. The description adds nothing about filtering or paging behavior, so baseline 3 applies.

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+resource (list bulk jobs/batches) and reveals the identifier role by saying it produces a batch ID. That implicitly separates it from get_batch_status and get_batch_sample_file, though no sibling is 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 two concrete triggers: the user asking what bulk jobs they have run, and needing a batch ID to feed a follow-up call. No explicit when-not or named alternatives, so it stops short of full routing guidance.

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