get_custom_recipe_details

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

No annotations provided, so description carries the full burden. It discloses that the tool returns plain text (not guided-cooking annotations) and directs users to update tools for annotation work. This adds useful behavioral context beyond schema, though it doesn't cover error cases or return structure.

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 concise sentences, first is front-loaded and zero waste. Each sentence adds distinct value: what it does, sibling distinction, return format, and pointer to update tools.

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?

Single-param tool with output schema present, so return structure is covered by schema. The description clarifies the custom-recipe scope and plain-text nature, which is significant. Slightly more could be said about content size or availability, but for this simplicity level it's solid.

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 0% and there's only 1 param (recipe_id). The description clarifies that recipe_id refers to a custom recipe (vs. general recipe), and the output is 'full text content' with plain ingredient/instruction text. With 1 param, baseline is near-max and description adds reasonable context.

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?

Specific verb+resource: 'Get the full text content of a recipe'. Clearly distinguishes from sibling get_recipe_details by noting it includes preparation instructions. Establishes scope ('custom recipes') explicitly.

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?

Provides a clear contrast with get_recipe_details (includes preparation instructions), which helps differentiate. However, it doesn't state when to choose this vs. the alternative, or when NOT to use it — no exclusions or conditions.

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