get_household_recipe

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

No annotations are provided, so the description carries the full disclosure burden. It mentions the GET endpoint and household scoping, but says nothing about authentication, error behavior on an unknown slug, or the shape of the returned data; the word 'read-only' appears only as an SEO keyword, not as a behavioral statement.

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 useful content is one short line followed by a long, redundant keyword list ('get household recipe, get recipe, fetch recipe, read recipe, retrieve recipe, view recipe, show recipe...') that repeats the same verb across synonyms without adding meaning. The keyword block consumes most of the text without earning its place.

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?

With no annotations, no output schema, and 0% parameter description coverage, the description should carry the load, yet it omits return contents, auth requirements, and error conditions. For a fetch tool in a crowded sibling space, this leaves material gaps.

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% for the single required recipe_slug parameter, and the description does not explain what a slug is, how to obtain one, or how it differs from a recipe id. The URL template {recipe_slug} is the only signal that it is a path parameter.

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 gives a verb and resource ('Get recipe ... Returns recipe data for the current household') and the URL template shows household scoping via /households/self/recipes/{recipe_slug}. However, 'Get recipe' is a near-tautological restatement of the name, and the description never distinguishes this tool from the numerous sibling recipe-fetch tools it sits beside.

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 statement of when to use this tool versus alternatives such as get_recipe, recipe_crud_get_one, or shared_recipes_get_one, despite many plausible siblings. The only hint is the HTTP path, which the agent must interpret on its own.

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