update_recipes

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

No annotations are present, so the description must disclose behavioral traits. However, it provides no information about whether the operation is destructive, requires authentication, or how it handles missing recipes. The description fails to add any behavioral context beyond the tool name.

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 only two words, which is concise but severely under-specified. It fails to provide enough information for an AI agent to understand the tool's purpose, thus it is not appropriately sized for the complexity of the tool.

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 complexity of the input schema (with many nested object types) and no output schema, the description is completely inadequate. It should at least explain the purpose of the 'body' array and what each recipe object represents.

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%, meaning the description adds no meaning to the parameters. The input schema is complex with nested objects (e.g., ingredients, steps), but the description does not explain the structure or usage of the 'body' parameter.

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 Many' is extremely vague. It suggests batch updates but does not specify what is being updated (though tool name implies recipes), nor does it clarify whether it updates existing recipes or creates new ones. The input schema includes an array of Recipe-Input objects where 'id' is optional, adding confusion about whether this is a create-or-update operation.

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 siblings like 'update_recipes_by_slug' (single recipe) or 'patch_recipes' (partial update). There is no mention of batch sizes, prerequisites, or filtering criteria.

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