list_batches

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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds valuable behavioral nuances beyond these flags: it explains why ordering is by brew date (Brewfather's _id ordering is not chronological) and discloses the compact row format, directing to get_batch for full records.

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 well-structured with an intro, ordering rationale, Args list, and Returns section. Each sentence earns its place, and the rationale for ordering is genuinely useful rather than filler. It is compact and easily scannable.

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?

Covers purpose, parameters, return values, and relationship to get_batch. With an output schema present, the compact row summary is sufficient. The tool is simple, and the description fully addresses all necessary aspects for selection and invocation.

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%, so the description must compensate, and it does excellently. Every parameter (status, limit, newest_first) is explained with its meaning, allowed values, and default behavior. The ordering nuance adds semantic depth to newest_first that the schema cannot convey.

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 phrase 'List brew batches, newest first by default' explicitly names the action and resource. It distinguishes from sibling tools like list_recipes (recipes vs batches) and get_batch (compact vs full record), making the purpose unmistakable.

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 includes 'Use get_batch for the full record,' an explicit pointer to a sibling alternative. It also explains the ordering rationale, helping the agent understand when this list tool is appropriate. It doesn't exclude other sibling tools like list_recipes, but the resource type (brew batches) makes the context clear enough.

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