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

Annotations already declare the safety profile (not read-only, open world, non-idempotent, non-destructive), but the description adds important behavioral context: billing is split by auth type, API-key runs use a USD wallet, pricing and key limits are checked on every step, and idempotency keys must be reused after a lost response. This goes meaningfully beyond the annotations and schema.

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?

The description is four dense but well-structured sentences. It front-loads the core action and then layers the auth-specific execution flow without filler. Every sentence contributes operational information.

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?

Given eight parameters, nested inputs, auth branching, and no output schema, the description covers the critical execution path and billing/idempotency behavior well. It does not mention what the tool returns or how to check run status, which is a minor gap given the sibling get_recipe_run exists.

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 100%, so the baseline would be 3, but the description adds semantic flow by linking max_credits to OAuth, and max_usd/quote_id/currency/idempotency_key to API-key execution. It helps the agent understand which parameters belong together in the quote-confirm-run sequence, which is more than the schema alone conveys.

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 clearly states the verb and resource: run a saved recipe or workflow with new material. It distinguishes itself from related siblings like list_my_recipes implicitly through 'saved recipe' and 'new material', but it does not explicitly contrast with resume_recipe_run or get_recipe_run. The purpose is nonetheless understandable without opening the 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 provides concrete guidance for OAuth versus API-key usage: OAuth uses max_credits, while API keys must first quote then confirm currency, max_usd, quote_id, and idempotency_key. It also explains idempotency-key reuse after a lost response. It lacks explicit guidance on when to use this versus resume_recipe_run, so it stops short of full routing guidance.

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