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

Adds real value beyond the annotations: confirms a hard 100-ID cap, promises caller-order preservation, and warns that missing_ids/closed_ids may come back, plus flags posting content as untrusted (prompt-injection relevant). Annotations already cover read-only/idempotent safety, so this is a solid addition rather than a full behavioral spec.

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?

A single dense sentence front-loads the core batching behavior and never repeats the name or title. The tail clause about summary mode is slightly compressed, but no words are wasted.

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?

With no output schema, the description does the work of indicating return shape: ordering, missing_ids/closed_ids, and the key detail fields. It stops short of stating response structure (e.g., whether unresolved IDs appear as nulls in position) or any rate/size caveats.

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?

With 0% schema coverage the description must carry the parameters, and it does: job_ids is bounded at 100 with order preserved, and details is explained as full (apply_url, source_url, untrusted content) vs summary (compact saved-list fields). The default of 'full' and the concrete summary field set remain unspecified.

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 batch scope: 'Read up to 100 job IDs in caller order'. An agent can distinguish it from single-item get_job by the batching and ID-list framing, 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?

The summary-vs-full distinction gives intra-tool usage guidance, but the description never says when to choose this over get_job or search_jobs. The caller must infer that this is the batch-hydration step after a search.

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