add_recipe

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

Discloses key behavior: 'Overwrites existing recipe with same name' and return format. However, no annotations are present, and the description does not cover authentication, error handling, or idempotency, which would be helpful for a mutation tool.

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?

Three focused sentences: purpose, usage tip, and behavior. Each sentence serves a distinct role with no redundancy. Front-loaded with primary action.

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 no output schema, the description adequately explains return fields. It covers purpose, parameters (with defaults), and overwrite behavior. Would benefit from error handling notes, but is sufficient for typical usage.

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 baseline is 3. The description adds value by noting default behaviors for 'searchTerms' and 'category', reducing friction. This extra context justifies a 4.

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?

Clearly states 'Add or update a recipe for meal planning and deal scoring', using specific verb and resource. Distinguishes from sibling tools like 'remove_recipe' and 'get_recipes'.

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 states 'USE WHEN: saving a new recipe or updating an existing one', providing clear context. Lacks explicit exclusion or alternative tool mentions, but the usage instructions are unambiguous.

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