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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description still adds real behavior: the result set is scoped to your own authored/saved/remixed content, and paging is offset-based with a total. No rate limits, but good added context.

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?

Three tight, front-loaded sentences with no filler; the scope distinction comes first and the filter/paging details follow. The state enumeration partially restates the schema enum, a minor redundancy.

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?

The output schema excuses explaining return values and annotations cover safety, but with 8 parameters, four of them enums, and zero schema descriptions, six parameters remain opaque — notably `action`, whose values give no hint of meaning. Incomplete for a tool of this breadth.

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 0% across 8 parameters, so the description must carry the burden — yet it only explains `state` and `offset`. The cryptic `action` enum (arm/run/reprompt), `model_kind`, `sort`, `tags`, `limit`, and `q` are undocumented in both schema and description.

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?

Specific verb+resource ('Page through the recipes you authored, saved or remixed') with an explicit scope statement. It names the sibling it is not ('which list_recipes never shows'), so an agent can pick between the two without opening either schema.

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 names the alternative (list_recipes) and the distinguishing condition (own private shelf vs. public list), plus a filter-on-state use case. It does not address when to prefer get_own_recipe over this list, so it stops short of full when/when-not coverage.

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