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

Beyond the readOnlyHint annotation, it discloses that pending_photos returns at most 30 private choices plus an observed version, that it neither claims recipes nor acknowledges notices, and that explicit confirmation is required before update_recipe recover_photo — 'never auto-attach or auto-confirm'. It also specifies ordering obligations for newly_assigned and fixes_asked, which annotations cannot convey.

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?

Front-loaded with the resource enumeration and trigger phrases, and every sentence carries operational content (confirmation gating, notice-handling rules). It is dense to the point of being a wall of text with an embedded '(section: photos)' aside that slightly interrupts flow, but little is redundant.

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-required-parameter read tool with full schema coverage, an output schema, and readOnly/openWorld annotations, the description supplies everything needed: what each section returns, pagination behavior for pending_photos, and the follow-up actions and confirmations required. No material gap remains for correct invocation.

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 100%, so the schema already defines every parameter; the description adds semantics the schema does not, notably the photos vs pending_photos split, why target_recipe gates that section, and the confirmation workflow around the returned choice. The limit/pending_cursor interactions remain documented only in the schema, so it does not fully exceed baseline.

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 enumerates the exact resources the tool returns (saved recipes, published recipes, versions, shopping lists, meal plans, ratings, pantry count) and anchors it with 'Same as My Kitchen on the website', which separates it from siblings like get_recipe or search_recipes. The verb itself is implied ('what the cook keeps') rather than stated as 'retrieve', which keeps it just below a top score.

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?

It gives explicit trigger phrases ('what did I save?', 'pull up last week's list', 'show my recipes') and explicitly scopes the photos section with a sample question. It also states conditional branches: pending_photos only for an explicitly requested interrupted photo save, and what to do when newly_assigned or fixes_asked are present, naming alternatives (update_recipe recover_photo, hand_back_recipe).

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