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

Annotations already declare the operation is a non-destructive write in an open world. The description goes beyond that by disclosing the charge threshold requiring user confirmation, the returned fields (charge_usd, per-step output, share_url), and the intended UX for the share link. It does not address idempotency/retry semantics, which the schema covers instead.

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?

Four sentences, front-loaded with the core action, then cost gating, then return/UX instructions. Tight and useful, though the trailing guidance about the share link is slightly run-on.

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?

There is no output schema, and the description compensates by naming the return shape (charge_usd, step outputs, share_url). Combined with the cost-confirmation rule and the recipe-slug source (list_recipes), an agent has enough to invoke and report correctly, though the inputs object semantics remain delegated entirely to the schema.

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 the schema documents recipe, inputs, review and idempotency_key in detail. The description adds only an indirect reference to estimated_cost_usd from list_recipes/get_recipe; it adds no syntax or constraints beyond the schema, making 3 the correct baseline.

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+resource ('Run an official recipe on our servers in one call'), which is concrete and distinguishable from run_tool/run_batch by the 'recipe' object. It does not explicitly contrast itself with those siblings, so it stops short of a 5.

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?

Gives one conditional workflow rule ('if estimated_cost_usd ... is above $0.50, tell the user before running it'), which is useful context. However it never states when to pick run_recipe over siblings like run_tool or run_batch, so the when-to-use guidance is only implied.

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