List Recipes

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

No annotations exist, so the description must carry behavioral disclosure, yet 'Get All' only implies a read operation and says nothing about pagination, ordering, scoping, response shape, or side effects. This is effectively no behavioral transparency.

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?

Two words is concise, but this is under-specification rather than economy; it does not earn its place because it conveys almost no usable 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?

Despite a high-complexity 19-parameter schema and no annotations, the description discloses nothing about filtering, pagination, auth/scoping, or relation to siblings. The output schema helps with return values but cannot compensate for missing selection and invocation semantics.

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% across 19 parameters, and the description names none of them. An agent gets no meaning for filters like tags, foods, search, orderBy, or requireAllTags beyond raw schema types.

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 is 'Get All', which conveys only a generic retrieval action and does not name the resource ('recipes') or the list's scoped behavior. It is close to a tautology of the title/name and provides no differentiation from siblings like list_shared_recipes or list_recipes_suggestions.

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?

'Get All' offers no guidance about when to call this tool over alternatives; no context, exclusions, or alternative conditions are given. With many sibling list tools, an agent cannot infer selection criteria from the description.

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