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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds context about membership roles and access control, which is useful, but it does not disclose any additional behavioral traits like pagination, ordering, or what happens when householdId is omitted. With annotations carrying the safety burden, a 3 is fair.

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?

Two sentences: the first states the core purpose (who and with which role), the second gives the usage context. No filler, front-loaded with the primary function, and every word adds value.

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?

For a simple read-only list tool with one optional parameter and no output schema, the description is adequately complete. It explains what it returns (members with roles) and when to use it. It does not describe the exact output format, but that is not required for this simplicity level. The only minor gap is not stating that the output is a list of members with role fields, but the description implies it.

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 100% for the single parameter, with a clear description of householdId and its behavior when omitted. The tool description does not add any extra parameter semantics beyond what the schema already provides, so the baseline of 3 applies.

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 the tool lists household members with their roles (owner, editor, viewer), which is a specific verb+resource. It also adds a use-case ('who can see or change their money') that distinguishes it from other list_* tools that list different entities. It is immediately clear what this tool does and what it is not.

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 provides a clear trigger: 'Useful when the user asks who can see or change their money.' This tells the agent when to reach for this tool. It does not explicitly exclude alternatives or name a sibling to compare against, but the use-case context is specific enough to route correctly.

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