get_recipe_as_format

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

No annotations are provided, so the description must disclose behavioral traits. It mentions that 'Template type will automatically be set on the backend' and that template names must be unique, which adds some value, but it omits critical details like required permissions, whether the operation is read-only (implied but not stated), and the response format.

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 poorly structured: a title-like preface, a one-line summary, an endpoint, a long keyword list, and a single parameter note. The keyword list is unnecessary bloat that distracts from useful information.

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?

For a tool with two required parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what the export returns, the format of the output, or any side effects. The single sentence about template uniqueness is helpful but insufficient.

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%, so the description carries the full burden. It explains that 'template_name' refers to a template and that names must be unique, but it does not clarify the 'slug' parameter at all, leaving half of the parameters undocumented.

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 the action ('Export recipes') and includes the endpoint, but the phrasing 'Get Recipe As Format' is unusual and lacks a clear, direct statement of what the tool returns. It is distinguishable from siblings like get_recipe, but the purpose could be clearer.

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 explicit guidance on when to use this tool versus alternatives such as get_recipe or bulk_export_recipes. The keyword list is not usage guidance; it's keyword stuffing.

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