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

Annotations already establish the safe, read-only, idempotent profile, and the description adds valuable behavioral detail beyond them: the taste_pending flag is derived, expresses a precise condition (no sensory tags, no rating, no tasted flip), and points to the update path. No contradiction with annotations.

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 sentences, with the core action front-loaded and the important derived-flag semantics in the second. Every clause earns its place; there is no filler or needless restatement of schema fields.

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 list tool with rich input and output schemas, the description is complete: it covers the operation, pagination/filtering capability, the one non-obvious semantic (taste_pending), and the cross-tool backfill path. The schemas provide the remaining mechanical details.

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 67%, so the schema carries most parameter meaning. The description adds specific semantic context for the taste_pending filter by explaining the flag is derived and that owed tastings can be backfilled via update_shot, going slightly beyond the enum text. Pagination and filter support are named generically, but limit/offset are already well documented in 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 opens with a specific verb and resource — 'List shot history' — and immediately adds scope with pagination and filtering support. The resource ('shots') clearly distinguishes it from sibling list tools such as list_beans and list_grinders, and the description is not a mere restatement of the title.

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?

Usage context is implied rather than explicit: the description suggests list_shots is the place to find shots with owed tastings and that update_shot is the follow-up to backfill them. It does not state when not to use the tool or name alternatives for other listing needs, so the agent must infer the boundary from sibling names.

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