households_mealplan_rules_get_one

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

No annotations are provided, so the description carries full behavioral burden. It says 'read-only' in the keyword list, which hints at a safe read, but doesn't state required permissions, error behavior for missing rules, or whether the rule is scoped to the logged-in user's household. For a zero-annotation tool, this is thin.

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 body is a single terse phrase, but it is followed by a long, redundant keyword dump that repeats the tool name and its tokens many times. The useful content is one line, surrounded by noise that does not earn 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 needed to explain what a mealplan rule is, what the response contains, and any household scoping. Instead it only restates the name and endpoint, leaving the agent under-informed for a tool with moderate domain complexity.

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%. The only parameter item_id is documented in the schema as a string with uuid4 format, but the description adds nothing about its meaning or where to obtain it. Baseline is 3 for one parameter, but the description fails to compensate for the zero coverage.

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 specific verb+resource: 'Get One — Households: Mealplan Rules. Get rule.' combined with the endpoint path GET /api/households/mealplans/rules/{item_id}, an agent can tell this retrieves a single mealplan rule. It doesn't explicitly differentiate from siblings like households_mealplan_rules_get_all, but the 'Get One' prefix and singular 'rule' imply single-item retrieval.

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 when-to-use or when-not-to-use guidance. The description never mentions how this differs from households_mealplan_rules_get_all (list rules) or how to obtain the item_id. All of that is left to inference from name and endpoint.

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