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

Beyond the readOnly/safe annotations, it discloses sort order, the page-vs-total distinction, a required paging loop, a staleness/restart rule, and the prerequisite of a linked Chop It account. That is substantial behavioral context an agent cannot infer from the 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?

Four short sentences, front-loaded with what is listed and its ordering, followed by paging mechanics and the read-only/account caveats. No filler.

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?

With an output schema present, return-shape explanation isn't required, yet the description still clarifies what the page field and total field mean. Combined with pagination and auth notes, an agent has everything needed to call this correctly.

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 already 100%, so baseline is 3; the description goes further by explaining the offset protocol semantically (start at 0, pass nextOffset, restart if data shifts). It doesn't add format or bound details beyond the schema's own minimum/maximum.

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 specific verb and resource (lists recipes in the user's Chop It library) plus scope qualifiers — includes imported/chat-saved recipes, ordered most-recently-updated first. It does not explicitly contrast with the sibling search_recipes, so an agent could still hesitate between a full-library listing and a search.

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 concrete operating conditions: iterate nextOffset until hasMore is false, collect every page before proposing edits, and restart the read if records change mid-pagination. It stops short of naming alternatives such as search_recipes or get_recipe for single-item lookups.

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