list_households_members

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

No annotations provided; description only reveals the action (returns users) without disclosing pagination behavior, authentication requirements, rate limits, or handling of empty/household context. Insufficient for an 8-parameter tool.

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?

Single sentence is concise but critically under-specified given the tool's complexity. It sacrifices necessary detail for brevity, making it minimally viable.

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 having an output schema, the description lacks context on pagination, filtering, and household scope assumptions. Incomplete for effective use.

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% with 8 parameters; description offers no explanation for any parameter (page, orderBy, perPage, etc.). Agent cannot understand how to invoke correctly.

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 'Returns all users belonging to the current household', specifying a verb (returns) and resource (users in current household). It distinguishes from sibling tools like list_households_cookbooks or list_households_mealplans by focusing on members.

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?

No guidance on when to use this tool versus alternatives, prerequisites, or exclusions. Among many siblings, the agent has no context for selection.

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