Submit an approved batch

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

The description adds rich behavioral context beyond the annotations: it re-runs per-application guards, honours daily limits and pacing delays, stops cleanly when the limit is reached, and respects campaign's maxBatchSize. These details are not inferable from the annotations alone and meaningfully inform the agent about side effects and stopping behavior.

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 sentences, each with substantive information. The primary action is front-loaded, and subsequent sentences add constraints and edge-case behavior. No filler or redundancy; the description is appropriately sized for the tool's complexity.

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 key behavioral aspects (guards, limits, stopping) but omits parameter semantics and any indication of return values or errors. Since there is no output schema, the agent is left to infer the response format. It is a functional, minimum-viable description but has clear gaps for a tool with 4 parameters and no output schema.

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 input schema has 0% description coverage, and the description does not explain any of the parameters (mode, headless, maxSubmissions). It mentions 'maxBatchSize' from the campaign, but not the 'maxSubmissions' parameter or the meaning of 'mode' or 'headless'. Since the schema provides no descriptions, the tool description should have compensated but fails to do so.

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's function: submitting every approved application in a batch. It uses a specific verb ('submits') and resource ('approved application in the batch'), and distinguishes itself from the sibling 'submit_application' which handles individual applications. The title reinforces this.

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 conveys that this tool is for submitting a batch of already-approved applications, implying it should be used after approval (e.g., after 'approve_batch'). It does not explicitly mention alternatives or exclusions, but the context is clear enough for an agent to select it over single-submission tools. Missing explicit 'when not to use' prevents a 5.

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