create_recipes_by_slug_duplicate

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

The description discloses the write operation (duplication) but lacks details on side effects, permissions required, or whether the original recipe is modified. No annotations are provided to supplement this.

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 a single sentence, which is concise but lacks necessary detail. It could be expanded without becoming overly verbose.

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 three parameters, no schema descriptions, and no annotations, the description is too minimal. It fails to explain how the slug identifies the source recipe, what the output contains (output schema exists but not described), and the role of accept-language.

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?

With 0% schema description coverage, the description must compensate for all three parameters. It only vaguely addresses the 'name' parameter ('new custom name'), ignoring 'slug' and 'accept-language'. No syntax or format details are given.

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 action (duplicate) and resource (recipe), and mentions the optional new name. However, it doesn't explicitly reference the required slug parameter to identify which recipe to duplicate, relying on the tool name and 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?

No guidance on when to use this tool versus alternatives (e.g., create_recipes for new recipes, patch_recipes_by_slug for updates). No exclusions or prerequisites are mentioned.

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