duplicate_pie

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

Discloses that the new pie starts with zero invested value, which goes beyond the annotations that only indicate it's not read-only or destructive. Missing details on side effects like the original pie being unchanged, but still strong.

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?

Five sentences plus structured Args/Returns section. Front-loaded with purpose and key behavioral detail (zero invested value). Every sentence earns its place.

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?

Covers all parameters, includes return type reference (PieDetails), and provides usage context with sibling tool. Given output schema exists, no need to detail return fields.

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 provides meaningful context: pie_id is the source pie ID obtainable from fetch_pies, name is optional with default behavior, and icon is optional. Adds value beyond bare schema.

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?

Description clearly states it clones an existing pie with identical allocations and settings, distinguishing it from create_pie which builds from scratch.

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?

Explicitly advises using this tool to create a variation of an existing pie without rebuilding, and references create_pie as an alternative for building from scratch.

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