save_recipe

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

The description states 'save to cache' implying a write operation, but lacks details on side effects (e.g., overwriting existing entries), persistence guarantees, or error conditions. With no annotations, this is insufficient for understanding behavioral traits.

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 short (one sentence), but conciseness comes at the cost of missing essential details. It is front-loaded with the action but omits necessary clarifications.

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?

With four parameters, no parameter descriptions, no annotations, and an output schema present but unaddressed, the description is critically incomplete. The agent cannot determine which parameters are required or how they are used.

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 description provides no explanation for any of the four parameters (doc_ids, summary, question, endpoint_ids). Given 0% schema description coverage, the description adds no value beyond the parameter names themselves.

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 uses a specific verb ('Save') and resource ('solved recipe') indicating the action. However, it does not clarify what constitutes a 'solved recipe' or how this tool differs from sibling tools like 'search_recipes' or 'call_api'.

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, prerequisites, or alternatives. The description does not mention when not to use it or how it fits into a workflow.

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