wealthbox.households.addMember

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only says 'Add member to a household,' which is a write operation, but does not disclose side effects, required permissions, behavior on duplicate members, or error conditions. The mention of 'raw body' hints at passthrough behavior but is insufficient for transparency.

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 two short sentences, front-loads the core purpose, and includes a concise usage hint. Every word earns its place; no filler or redundancy. It is appropriately sized for the tool's complexity.

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?

The tool has four parameters including a nested body object and an enum, but no output schema or annotations. The description covers the basic operation and parameter relationship, but does not explain return values, possible errors, or the meaning of 'id' (e.g., contact ID vs member ID). It is adequate for a simple CRUD-like operation but leaves several contextual 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 coverage is 0%, so the description must compensate. It explicitly clarifies the relationship between parameters by stating 'Provide household_id and either id+title or raw body,' which is not evident from the schema alone. This explains the required household_id and the exclusive alternative between id+title and body, adding useful semantic meaning beyond the raw schema.

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 specific action ('Add member to a household') with a clear verb+resource structure. It distinguishes itself from the sibling tool 'wealthbox.households.deleteMember' by indicating addition rather than removal. The scope is 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 provides no guidance on when to use this tool versus alternatives. It gives a brief invocation hint ('Provide household_id and either id+title or raw body') but never references alternative tools or scenarios where another tool would be more appropriate. No when-to-use or when-not-to-use information is present.

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