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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states the basic action without detailing consequences (e.g., adding the user to the household), error cases (e.g., invalid or expired token), or side effects. Important behavioral aspects are omitted.

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 a single, focused sentence with no extraneous information. It is appropriately concise for a simple tool, and all words add 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?

Given the simplicity of the tool (one parameter, no output schema), the description is minimally adequate. However, it does not cover what happens after successful acceptance, error handling, or prerequisites for use. A more complete description would mention the expected outcome and possible failure modes.

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 describes a single 'token' parameter with no description (0% coverage). The description adds context by stating that the token comes from the invite link, which helps an agent understand the source of the value. However, it remains vague and does not specify whether the token is the full link or just a code, nor its format.

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 action (accept), the target (household invite), and the method (using the token from the invite link). It effectively distinguishes from sibling tools such as parent_invite_household_member and parent_leave_household by specifying the invite acceptance action.

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 lacks any guidance on when to use this tool versus alternatives. No prerequisites, conditions, or exclusions are mentioned. For example, it does not clarify that the user must have received an invite and have the token, nor does it reference related tools like parent_my_household for verification.

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