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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the agent knows this is a contained write with no external side effects. The description adds useful scoping about what content qualifies, but says nothing about duplicate titles, whether an existing recipe is overwritten, or what identifies the newly saved recipe. With the safety profile already carried by annotations, this is adequate but not rich.

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 short sentences, front-loaded with the action and resource, then the qualifying input types, then the redirect to the sibling. Nothing is repeated or wasted.

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 non-destructive write with a fully documented 8-parameter schema and no output schema, the description covers what an agent needs to choose and invoke it correctly. The only gap is post-save behavior — duplicate handling and the identity of the created recipe — which would be nice but is not blocking given the annotation profile.

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 100%, so every parameter including cookbookId, tags, and the ingredient unit semantics is already documented in structured data. The description adds no parameter-level guidance beyond what the schema provides, which is the baseline-3 case for full coverage.

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 states a specific verb and resource — 'Save a recipe to the user's Recipe One library' — and immediately delimits the accepted input forms (written/adapted in chat, pasted text). It explicitly distinguishes itself from the closest sibling by pointing links at import_recipe_from_url, so an agent can pick correctly 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 gives both sides of the routing decision: use this for chat-authored or pasted recipe text, and use import_recipe_from_url for a link. That is an explicit when-to-use plus a when-to-use-something-else, with no inference required.

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