List batches

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds that provider scopes, locks, and credits apply, which is useful behavioral context, but it remains vague and does not detail rate limits, pagination, or response 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?

The description is short and front-loads the endpoint, but 'Read operation' repeats the readOnlyHint annotation and 'Current Bannerbear V5 operation' is boilerplate. Those lines do not earn their place as much as missing pagination or usage details would.

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 should explain return values or pagination, but it does not mention either. For a list tool with an undocumented page parameter and no usage guidance, it leaves important agent-relevant context unaddressed even though annotations cover the safety profile.

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?

Schema description coverage is 50%: the account parameter is documented in the schema, but the page parameter is not. The tool description mentions neither parameter, so it fails to compensate for the undocumented page argument or add any parameter meaning beyond the 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?

The description states the specific HTTP verb and resource with 'GET /v5/batches', making clear this is a read endpoint for batches. It does not explicitly differentiate from siblings such as get_batch or list_publications, but the plural resource name provides some distinction.

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 or mention of alternatives. The only contextual sentence is a generic note that provider scopes, locks, and credits apply, which does not help the agent choose this tool over others.

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