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

Annotations only declare the safety quad (non-readOnly, non-idempotent, non-destructive). The description adds real behavioral context the annotations cannot: snapshot semantics (later curator edits don't affect your copy), what is and isn't carried over (questions/model/settings yes, prompt wording no), and the name-default behavior. This is exactly the value-add expected beyond structured fields.

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 core copy action and efficient overall, but update_recipe is referenced twice with overlapping phrasing ('write your own prompt on the copy' and 'Edit the copy'), which is mild redundancy in an otherwise tight description.

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?

An output schema exists so return values need no explanation, and the description covers purpose, copy limitations, snapshot guarantees, and alternatives. The only shortfall is that the 0%-coverage parameters (tags, description) and the required/optional mismatch are left unaddressed.

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 0%, so the description must carry parameter meaning across 4 params—but it only addresses the name default and never explains tags or description. Worse, it asserts 'Every field is optional,' which conflicts with the schema's required recipe_id, leaving an agent potentially misled about what can be omitted.

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 ('Copy') and resource ('catalog recipe onto your own shelf'), and explicitly distinguishes itself from siblings like update_recipe, create_recipe, and start_recipe_run. An agent can tell exactly what this does and does not do without opening any 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?

Names the alternatives and the conditions selecting them: use update_recipe to edit the copy, start_recipe_run for run recipes, create_recipe to author your own. It also states the exclusion ('A run recipe cannot be copied'), which is precise routing.

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