list_recipes

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

No annotations exist, and the description fails to disclose any behavioral traits such as pagination, authentication requirements, or rate limits. The agent cannot infer basic behavior like whether this returns all recipes or supports filtering.

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?

While extremely concise at two words, the description is under-specified and fails to convey essential information. True conciseness should include critical context without verbosity, but here it omits everything.

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?

Despite having 19 parameters and a complex schema, the description provides no context. The existence of an output schema does not excuse the lack of description for such a feature-rich tool.

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?

With 0% schema description coverage and no mention of parameters in the description, the agent receives no additional meaning beyond the raw schema. Parameters like 'search', 'orderBy', and 'tags' require explanation that is entirely absent.

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 'Get All' is a tautology that only restates the tool's implied action of listing. It does not specify the resource (recipes) or provide any distinguishing information from sibling tools like list_recipes_suggestions 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?

No guidance is provided on when to use this tool versus alternatives. The description lacks any context about filtering, searching, or pagination, leaving the agent without direction.

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