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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile needs no restating. The description adds genuine behavioral context beyond that: the result set is scoped to ownership or membership, and each entry includes a recipe count. Pagination and ordering behavior remain undisclosed, which keeps it below a 5.

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 short clauses, front-loaded with the usage trigger followed by what the call returns. Every phrase carries information; nothing is repeated from the title or annotations.

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 parameterless read-only list tool with full annotation coverage, this is nearly sufficient: the agent knows the trigger, the scope, and the payload shape. Only minor gaps remain (no mention of empty results or ordering), and no output schema exists to cover those.

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 the baseline is 4; there is nothing for the description to disambiguate. The description correctly implies a simple no-argument call rather than hinting at filters that do not exist.

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 gives a specific verb and resource ("Lists the cookbooks") and clarifies the domain term with a parenthetical ("recipe collections"). It also defines the scope precisely as "the cookbooks the user owns or is a member of," which no sibling tool covers.

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 trigger is explicit: use it when the user asks about cookbooks or when a cookbook id is needed as a prerequisite for another tool. It stops short of naming alternatives (e.g. search_recipes for finding recipes rather than collections) or stating when-not to call it, so it does not reach a 5.

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