List Recipes Exports

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

With no annotations, the description carries the behavioral disclosure burden. 'Get' weakly implies a read-only list operation, but the description does not state side effects, permissions, pagination, or what 'formats and templates' means in the response. It adds little beyond the title.

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 extremely short and front-loaded with the key noun phrase, containing no filler. It is concise, though it borders on under-specification.

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 is simple, with one optional parameter and an output schema present, so the lack of return-value explanation is less critical. Still, it lacks sibling differentiation and parameter explanation, making it minimally viable rather than complete.

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 only parameter, accept-language, has 0% schema description coverage. The description does not mention that the parameter controls language/localization, whether it is optional, or how it affects the response. With no schema-level documentation, the description was the only chance to explain it and missed that opportunity.

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 names a specific verb and resource, 'Get Recipe Formats And Templates', which conveys more than the bare title and suggests it lists available export formats. However, it does not differentiate itself from related export endpoints such as list_recipes_by_slug_exports or list_recipes_bulk_actions_export.

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 endpoint versus alternatives, no exclusion criteria, and no mention of related by-slug or bulk-export siblings. An agent must infer usage from the tool name alone.

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