list_recipes_shared_by_token_zip

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

No annotations are provided, so the description must fully disclose behavioral traits. It states the output is a Zip file containing the recipe and original image, but does not mention what happens if the token_id is invalid, expiration of tokens, rate limits, authentication requirements, or whether the operation is destructive or read-only. This lacks transparency for an unannotated tool.

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 a single sentence, front-loaded with the key action. It is concise with no unnecessary words. However, it may be too short given the need for more context.

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?

The tool has one parameter, no output schema, and no annotations. The description is minimal and does not cover the return format of the Zip file, potential errors, or how the token relates to the recipe. Given this simplicity, the description is incomplete for effective use.

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%, and the description does not explain the sole parameter `token_id`. The parameter is a UUID, but its purpose (e.g., a shared recipe token), how to obtain it, or constraints are not mentioned. The description adds no 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?

The description clearly states the tool's purpose: retrieving a recipe and its original image as a Zip file. It uses a specific verb ('Get') and resource (recipe + image in zip). However, it could be more precise about what 'get a recipe' entails (recipe data or just the file?). The name 'list_recipes_shared_by_token_zip' is slightly misleading as 'list' implies multiple but the description says 'Get' a single recipe. Among siblings like get_recipes_shared_by_token and list_shared_recipes, this one distinguishes by mentioning Zip output.

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?

There is no guidance on when to use this tool versus alternatives such as get_recipes_shared_by_token (which likely returns JSON) or list_shared_recipes (which lists shared recipes). The description does not specify any context, prerequisites, 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.