get_household

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

The description discloses a key behavioral trait: 'Returns onboarding guidance if not yet configured.' It implies a read-only operation with no side effects, which is appropriate for a configuration retrieval tool. However, without annotations, it could further elaborate on potential latency or data freshness.

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 extremely concise (two sentences) with no fluff. It front-loads the main action and purpose, then adds usage context. Every sentence contributes value, making it efficient for AI parsing.

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?

Given the absence of an output schema, the description fully explains the returned data (people, dietary restrictions, etc.) and the special case of unconfigured states. It covers all necessary details for a simple configuration read tool, requiring no additional information.

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?

The input schema has zero parameters, so schema description coverage is 100%. The description adds value by explaining what the tool returns, compensating for the lack of parameters. It ensures the agent understands the output even without parameters.

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 clearly states it retrieves household configuration, listing specific items like people, dietary restrictions, preferred stores, and servings. This distinguishes it from sibling tools like update_household (write) and get_pantry (different resource), making the purpose unambiguous.

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 explicitly provides usage scenarios: 'USE WHEN: checking current setup before meal planning, verifying store preferences.' This offers clear guidance on when to invoke this tool, and the context signals show no required parameters, simplifying decision-making.

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