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

Annotations already declare this operation read-only, idempotent, and non-destructive. The description adds meaningful behavioral context by explaining the derived taste_pending flag's exact condition and pointing to update_shot for backfilling, which goes beyond what annotations provide.

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, each earning its place: the first states the core purpose and capabilities, the second explains a non-obvious derived flag. Purpose is front-loaded and there is no repetition of schema details.

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?

Given the output schema exists and annotations cover safety, the description is largely complete: it explains pagination, filtering, and the meaning of the important derived flag. It could more explicitly state that the taste_pending filter can be combined with other filters to find owed tastings, but that is implicitly clear.

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?

The schema already documents limit, offset, and the filters and their ranges/enums. The description's taste_pending explanation largely mirrors the schema's own filter description, though it does add the backfill pointer. With 67% schema coverage, the description provides moderate added value but doesn't compensate heavily for the undocumented filters wrapper.

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 action and resource: 'List shot history'. It also mentions the two key capabilities (pagination and filtering), which clearly differentiates it from sibling list_* tools and from mutation tools like update_shot.

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 makes obvious when list_shots is appropriate: to retrieve shot history with pagination/filtering. It also references update_shot as the follow-up for backfilling owed tastings, giving useful workflow context. However, it does not explicitly state when not to use this tool or compare it with an alternative.

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