Parse job postings (batch)

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-annotated behavior: the 1–20 batch limit and the guarantee that results come back in the same order as inputs. It omits per-item failure semantics (does one bad posting fail the whole batch?) and cost/latency implications of batching.

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 sentence, front-loaded with the action and scope, with the ordering guarantee appended. Nothing is wasted and nothing needs to be re-read.

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 is the only source for what a 'parsed posting' returns, and it only says the results are order-matched — it never mentions the extracted fields (salary, skills, flags) that the input schema hints at. For a batch-mutation-free parsing tool with one parameter this is workable but leaves the return shape and partial-failure behavior undefined.

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 parameter, an array, and the top-level 'postings' property carries no description in the schema (reported coverage 0%). The description compensates partly by stating the accepted cardinality (1–20) and output ordering, but says nothing about what each posting object must contain (title required) or how the description field drives extraction — that information lives only in the nested item schema.

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 ('Parse ... job postings') plus the batch scope ('1 to 20 ... in one call'), which implicitly separates it from the singular sibling parse_job_posting. However, it never names that sibling or say 'batch' explicitly in the description body, so the differentiation is inferred from the number 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?

There is no when-to-use guidance, no mention of when to prefer the singular parse_job_posting, and no prerequisites or exclusion conditions. The only hint is the cardinality range, which implies 'use this for multiple postings' but leaves the choice between siblings to the agent.

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