List prepared batches

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

The readOnlyHint annotation already signals that this is a safe read operation. The description adds that it returns recent batches with status and counts, which is useful but does not disclose additional behavioral traits such as default ordering, pagination, or whether the output is a list. It does not contradict the annotation.

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 single, short sentence that contains no redundancy or filler. Every word contributes to conveying the core function, making it highly concise and 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?

For a simple read-only list tool with one optional parameter and no output schema, the description is minimally sufficient. It covers the basic purpose but does not elaborate on the return shape, default limits, or the specific meaning of 'per-state counts,' leaving some gaps given the lack of an 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?

Schema description coverage is 0%, and the description does not mention the 'limit' parameter at all. While the parameter name is somewhat self-explanatory, the description fails to provide any definition, default behavior, or context about how limiting works, leaving semantics undocumented.

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 identifies the resource (recent batches) and the output (status and per-state counts), which is specific enough to understand the tool's purpose. However, it does not explicitly distinguish this from sibling list tools like list_queue or list_applications, though the resource name 'batches' offers some differentiation.

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 the tool is used to view recent batch statuses, but it provides no explicit guidance on when to prefer this over alternatives or when not to use it. No exclusions or alternative tool references are mentioned.

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