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

With annotations already covering the safety profile, the description adds substantial non-obvious behavior: the row is unchanged, nothing is published, a human curator decides, and the outcome is observable through `get_own_recipe`.`submission`. It does not state ownership/permission requirements explicitly beyond the phrase 'you own', which is the only notable gap.

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 sentences with no filler; the core action and the withdraw toggle are front-loaded, followed by the clarifying non-effects and the review lifecycle. Every sentence carries information an agent needs.

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 two-parameter state-toggle tool with an output schema and full annotations, the description covers the complete lifecycle: submit, withdraw, curator decision, and resubmission clearing a prior decline, plus where to read the result. Nothing an agent needs to invoke it correctly is missing.

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 the parameter burden. It defines the meaning of `submitted: false` (withdrawal) well, but leaves the default/omitted behavior of `submitted` and the semantics of `recipe_id` to inference, so it only partially compensates for the undocumented schema.

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 first sentence states a specific verb (offer/withdraw) on a specific resource (a recipe you own) and names the destination (the official catalog). It also implicitly separates this from publish_recipe by stating the submission is an offer that a curator reviews rather than an immediate publication.

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 clear when-to-use guidance in both directions: offer with the default, withdraw with `submitted: false`, and it notes resubmission after a decline. It stops short of explicitly naming the alternative tool (publish_recipe) for agents who actually want to publish, so routing is inferred from 'does not publish it' rather than stated.

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