Render, compile & log a whole batch

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

The description discloses side effects (auto-logging to tracker, caching) and the two operational modes, which adds value beyond the schema. However, with no annotations, it lacks details on idempotency, error behavior, and permissions required.

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 focused paragraph that front-loads the main action and includes necessary technical details without excessive verbosity. It could be slightly more concise but is well-structured.

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?

The description covers the core batch behavior and auto-logging but omits mention of optional cover letter support and template options (resume/cv). Given the complex input schema and lack of output schema, more details would improve completeness.

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?

The description explains the conditional logic between 'content' and 'reuseFrom' parameters, clarifying that 'content' is only needed for GENERATE jobs and for others 'reuseFrom' is used to resolve content automatically. This adds significant guidance beyond the schema descriptions.

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 clearly states the tool renders, compiles, auto-logs, and caches a batch of jobs in one call. It distinguishes from sibling tools like 'batch_plan' (planning) and 'render_and_compile' (per-job) by emphasizing no per-job round trip and referencing the batch plan.

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 that this tool should be used after 'batch_plan' and instead of calling 'render_and_compile' for each job. It explicitly mentions the two modes (GENERATE vs reuse) but does not explicitly state prerequisites or when to avoid using it.

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