list_recipes

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

With no annotations, the description carries the burden. It discloses the return format (summaries with name, slug, description, metadata) but does not mention pagination behavior, ordering, or any other behavioral aspects. The addition of return fields adds value, but the tool's behavior beyond that is underexplained.

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 two sentences, front-loaded with the tool's purpose and a concise listing of the return fields. Every sentence earns its place with no fluff or repetition.

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 simple list tool with two pagination parameters and no output schema, the description adequately covers purpose and return information. It could be more complete by explicitly mentioning pagination or any defaults, but the schema already documents those, so the description is sufficiently complete for the tool's simplicity.

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 100% for both page and perPage parameters, so the baseline is 3. The description adds no additional parameter semantics; it only describes the output, not the parameters, so it does not exceed the schema's documentation.

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 and resource: 'List all recipes in Mealie' and distinguishes from siblings like get_recipe by stating it returns summaries with name, slug, description, and metadata. This clearly communicates the tool's scope and 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?

The description implies usage by saying 'List all recipes' but does not explicitly alternate with get_recipe or other list tools. It provides clear context for what the tool does, but no exclusions or guidance on when to choose this over alternatives.

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