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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real value by disclosing the return type (step-by-step screens/buttons/fields) and that it performs no action itself, plus the fact that AnyList has no public API — context an agent would otherwise lack.

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?

Short and front-loaded: scope first, then what it returns and the follow-on tools, then the supporting API fact. The 'from ChatGPT, Claude or any AI agent' clause is mild padding but does not obscure the core instruction.

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 zero-parameter, read-only tool with no output schema, the description mostly suffices but leaves the central question unanswered: which recipe is read and what the returned content actually looks like. The 'no public API (checked 25 Oct 2026)' note is useful orientation but does not fill that gap.

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 tool takes zero parameters, so there is nothing for the description to disambiguate at the schema level; baseline 4 applies. The one residual gap is that with no identifier parameter, the description never explains how the target recipe is determined (presumably from browser state).

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 verb and resource ('Read recipe in the user's own AnyList account') and distinguishes the tool from actual browser actions by saying it 'opens nothing by itself'. However, it then says the tool 'Returns how to do it in AnyList step by step (screens, buttons, fields)', which makes it unclear whether the tool returns recipe content or a navigation guide — and with zero parameters, it never says which recipe is read or where it comes from.

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 explicit sequencing guidance — use this first, then perform the steps with the cotlet_browser_* tools in the AnyList Cloud Browser — which is genuinely useful routing. It stops short of saying when NOT to use it, e.g. how it relates to the sibling cotlet_app_guide or anylist_create_recipe, so the agent must infer the boundary.

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