get_recipe_asset

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

The description lacks behavioral details beyond the fact that it is a GET request and returns an asset. With no annotations, it should disclose whether it is read-only, what the response format is (e.g., binary blob), or any error conditions.

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 very concise, consisting of three short lines: title, endpoint pattern, and a one-line summary. No fluff, but it omits necessary details, so it is not optimally structured for completeness.

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 annotations or output schema, the description should explain what a 'recipe asset' is (e.g., image, PDF, other file) and how it differs from similar tools like 'get_recipe_img'. It fails to provide this, making it incomplete for reliable tool selection.

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?

The input schema has 0% description coverage for its two parameters (recipe_id, file_name). The tool description adds no additional meaning or context about these parameters beyond their names, leaving their purpose ambiguous.

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 states 'Get Recipe Asset' and 'Returns a recipe asset', clearly indicating the action and resource. It differentiates from sibling tools like 'upload_recipe_asset' through the verb 'Get', but does not explicitly distinguish from 'get_recipe_img' or others.

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 alternatives. There is no mention of prerequisites, context, or scenarios where this tool is appropriate.

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