find_batches

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

With no annotations, the description carries the full burden and does well: it documents the returned fields, the sort order (undated/Planning batches lead, then by brew date, ties by higher batch_no), and that an empty status means any. It omits read-only confirmation, result limits/pagination, and auth requirements, which keeps it from a 5.

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?

Front-loads the purpose, then parameters, then return shape, then next-step routing — a sensible order with no filler. The sort-order clause is detailed but earns its place since ordering is otherwise unknowable.

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?

Despite an output schema existing, the description usefully summarizes the returned dict and ordering, and it fully documents both zero-coverage parameters. An agent has everything needed to call it correctly and consume the result.

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 enums are absent, so the description must compensate — and it does: name is defined as a case-insensitive substring match, status is enumerated (Planning, Brewing, Fermenting, Conditioning, Completed, Archived) with empty meaning 'any'. Both parameters are fully specified beyond the bare 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?

States a specific verb+resource ('Find batches') with the exact matching semantics (case-insensitive substring on name, filter on status). It also distinguishes itself from siblings by telling the agent to use the returned id with get_batch/get_readings/update_batch, making the search-vs-retrieve split explicit.

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?

Gives clear usage context: this is the discovery entry point, and the resulting id feeds get_batch, get_readings, get_brewtracker, and update_batch. It does not state when NOT to use it (e.g., if the id is already known, call get_batch directly), so it stops short of full when/when-not guidance.

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