update_recipes_by_slug_image

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

With no annotations, the description bears full responsibility for behavioral disclosure. 'Update Recipe Image' implies mutation but does not state whether it overwrites the existing image, whether it creates a new image if none exists, or any side effects. No permissions or limitations are mentioned.

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 extremely concise (only two words), but this brevity sacrifices usefulness. It is front-loaded but lacks any substantive information. Every word earns its place, but the description fails to convey necessary details.

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 the tool has 4 parameters, no annotations, and a two-word description, it is completely inadequate. The description does not explain the operation context, parameter roles, or outcome. Even though an output schema exists, the tool description itself is insufficient for correct use.

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 the description says nothing about parameters. The agent receives no guidance on the meaning of 'slug', 'image' (binary data), 'extension', or 'accept-language'. This is a critical gap for correct parameter usage.

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 'Update Recipe Image' clearly indicates a mutation operation on a recipe image. However, it does not specify that the update is scoped to a specific recipe by slug, nor does it differentiate from the sibling create tool which might also set an image. The resource is clear but the exact scope is implicit from the tool name.

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?

No guidance is provided on when to use this tool versus the sibling create_recipes_by_slug_image or delete_recipes_by_slug_image. The description lacks any context about prerequisites, preferred scenarios, or exclusions, leaving the agent to guess.

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