recipes_units_create_one

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

The description states 'Create One' implying creation, but no annotations exist. It lacks disclosure of behavioral traits such as required permissions, idempotency, or side effects. For a creation tool, this is insufficient.

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 extremely short, but this under-specifies the tool. It is not concise; it is inadequate. A single line without structure does not earn 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?

Given the tool has many parameters, no output schema, and no annotations, the description completely fails to provide necessary context. It is insufficient for an AI agent to understand 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 description coverage is 0%. The description provides no explanation of parameters like name, aliases, fraction, etc. The user must infer meaning from the schema alone, which is vague (e.g., 'Standardunit').

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 'Create One' barely indicates creating a single unit, but it is essentially a tautology of the tool name. It does not specify the resource (units) explicitly, relying on the name for context.

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 recipes_units_update_one or recipes_units_merge_one. The description offers no context for selection.

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