upload_recipe_asset

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

No annotations provided, so description carries full burden. Only states 'Upload a file to store as a recipe asset' without disclosing file type restrictions, size limits, overwrite behavior, or authorization requirements.

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?

Very concise with only three lines, but it repeats the tool name and includes implementation detail (HTTP method/path) that may not be necessary for an agent. Could be slightly more informative within the same length.

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?

No output schema, no annotations, and only minimal parameter info. The description does not explain the return value, whether assets are immediately available, or any constraints, leaving significant gaps for agent understanding.

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 50%. The description adds context that the 'file' parameter must be an absolute path to a local file, which is not in the schema. However, other parameters (slug, icon, name, extension) have no additional description.

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 the verb 'Upload' and resource 'Recipe Asset', and includes the HTTP endpoint. Distinguishes from sibling tools like 'get_recipe_asset' which retrieves assets.

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 explicit guidance on when to use this tool vs alternatives. There are siblings like 'create_recipe_from_image' that also involve file uploads, but the description does not differentiate usage contexts.

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