Get Households Self Recipes By Recipe Slug

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says the tool returns data, so the read-only nature is inferable, but it does not explain authentication/authorization requirements, what 'self' means, scoping assumptions, or error behavior.

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 a single tight sentence with no wasted words and the scope is front-loaded. However, it is under-specified for the number of parameters and the absence of annotations, so this is brevity rather than well-rounded conciseness.

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 a simple read with an output schema, so return-value documentation is not the main gap. But with 0% parameter coverage, no annotations, and no alternative guidance, the one-sentence description is not complete enough for an agent to call it confidently in the right context.

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%, and the description adds no meaning to either parameter. It does not explain that recipe_slug selects which recipe to fetch or what accept-language controls, leaving the agent with only parameter names and no semantic guidance.

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 a clear action ('Returns recipe data') and a clear scope ('current household'), so an agent can tell this is a read of household-scoped recipe data. However, it omits the key 'by recipe slug' mechanism and does not explicitly differentiate it from siblings like get_recipes_by_slug or the explore recipe-by-slug tool, preventing a 5.

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 phrase 'for the current household' supplies useful context and implies the tool is for household-scoped recipe retrieval. It gives no explicit guidance about when to choose this over sibling recipe-fetching tools and no exclusions, so guidance is mostly implied rather than stated.

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