Sync a user's complete distinct-beers list into the cache

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

Beyond annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false), the description discloses key behaviors: 'Offset-paged and resumable: fetches max_pages per call and persists progress; run again until another_run_needed is false.' It also mentions the ~100 calls/hour rate limit and clarifies the cache is populated. This adds rich behavioral context without contradicting any annotation.

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 dense yet efficient, with each sentence earning its place: purpose, rationale, behavior, downstream consumers, and usage note. It is well-structured with the core action front-loaded and no redundant filler. Despite its length, it is concise in conveying all necessary information.

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 complexity of a paginated, resumable sync operation, the description covers all essential aspects: what is fetched, the source, the caching target, the pagination and persistence behavior, the termination condition (another_run_needed), rate limits, and optional username handling. It also links to the cache tools it feeds, providing a complete picture for correct invocation. No output schema exists, but the description adequately hints at the return flag.

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 100% and both parameters already have descriptive text. The description reinforces the meaning (e.g., 'Omit username for your own account', 'Keep modest to respect the ~100 calls/hour rate limit') but does not materially extend the schema semantics. It does tie the usage of max_pages to the resumable behavior, but that's a minor addition, so a baseline 3 is appropriate.

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+resource: 'Fetch a user's COMPLETE distinct-beers list ... into the cache from user/beers.' It clearly differentiates from siblings by emphasizing 'cheapest way to get full has had coverage' and explicitly contrasting with user/checkins, and by noting it feeds the cache tools. No ambiguity about what it does.

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 gives explicit guidance on when to use: 'This is the cheapest way to get full has had coverage' and 'unlike user/checkins, it pages fully for any public/friend account.' It also states the resumable pattern ('run again until another_run_needed is false') and advises on max_pages to respect the rate limit. Names the alternative (user/checkins) and the condition.

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