create_food

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

With no annotations, the description carries full burden. It discloses a key behavioral trait: Tandoor lacks duplicate detection, so creating a duplicate will silently succeed. It also adds domain-specific rules about naming, which are not visible in the schema or annotations.

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?

Two sentences with no fluff. The first sentence is the core purpose; the second packs essential usage warnings and naming rules. Every word 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?

For a simple create tool with an output schema, the description covers all necessary context: what it does, how to avoid duplicates, and naming conventions. It is fully sufficient for an agent to use it correctly without additional info.

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 100%, so baseline is 3. The description adds meaning to the 'name' parameter by specifying it should be a plain noun and not a prepared form, and suggests that preparation belongs in the note (likely the 'description' parameter). This adds value beyond the 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?

Clearly states 'Create a new food (ingredient)' with a specific verb and resource. The description distinguishes itself from siblings by emphasizing the need to search first due to missing duplicate detection, making it clear this is for creating new entries only.

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 instructs 'Search first' and explains why (no duplicate detection), effectively guiding the agent to use search_foods before invoking this tool. Also provides naming conventions to avoid incorrect usage, such as storing plain nouns rather than prepared forms.

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