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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavior beyond those annotations: the id is a per-account, 1-based row number, safe to show, and is the exact value other tools expect back. It does not mention pagination or ordering, but the output schema reduces the need for that.

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?

Two tight sentences: the first covers purpose and filters, the second explains the crucial ID semantics. No waste, no repetition of schema fields, and the most useful operational note (what the id means) is included.

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 read-only, optional-filter list tool with an output schema, the description covers the main behavioral contract and ID expectations. The only notable gaps are not saying 'locked recipes' explicitly and not mentioning where bean_id/grinder_id/machine_id values come from, but these are minor given the title, schema, and sibling naming.

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 coverage is only 25% (status is documented; bean_id, grinder_id, and machine_id are not). The description adds meaning by grouping the three integer parameters under 'equipment' and by naming 'status' as another filter, which helps an agent infer their role. It does not, however, explain what each equipment parameter refers to or how to source valid IDs.

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 a specific verb ('List'), a resource ('recipes'), and the available filter dimensions ('equipment and status'), which clearly separates this from sibling list_beans/list_grinders/list_machines. The only weakness is that the description omits the 'locked' qualifier from the title, leaving slight ambiguity about whether this returns all recipes or only locked ones.

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 usage: call this when you need a recipe list, optionally filtered by equipment or status. It does not provide explicit when-not-to-use guidance or name alternative tools, but the sibling set makes resource-based selection reasonably direct. With four list_* siblings, some explicit routing would have improved it.

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