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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. Beyond that the description adds real behavior: results are newest-first and scoped to 'recent' jobs only, implying the listing is truncated rather than exhaustive. It doesn't spell out how far back 'recent' reaches, keeping it from a 5.

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?

Two sentences, zero filler: the core action and field set come first, then the recovery use case and the sibling handoff. Every clause earns its place.

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 list tool with rich annotations, a fully documented lone parameter, and a pointer to the detail sibling, the description covers what an agent needs to call it correctly. The only unresolved point is how many/which 'recent' jobs are visible, which is minor.

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?

Only one optional parameter at 100% schema description coverage, so the schema already fully documents 'limit'. The description adds no format, range, or paging guidance beyond the implicit notion of recency, making this the baseline case where the schema does the work.

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 ('List your recent bulk jobs'), names the fields returned (id, state, error class, timestamps) and the sort order, and explicitly distinguishes itself from bulk_status. An agent can choose between the two sibling tools without reading either schema.

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 a concrete motivating use case ('recover a lost job id') and routes to bulk_status for details, which is a clear use-this-not-that signal. It doesn't state an explicit exclusion case, so it falls short of a 5.

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