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

Annotations flag this as destructive and non-idempotent; the description adds non-obvious behavior beyond that: invite sends an email, Family caps at 5 members, Chef allows 15 invites total, and destructive actions require confirmation. That is exactly the context annotations cannot convey.

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 dense and front-loaded: reads first, writes second, confirmation rule third, sibling pointer last. Every clause carries information about actions, side effects, or limits, with no filler.

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 10-action tool with 7 parameters and no output schema, the description covers what each action does, side effects, quotas, and confirmation requirements. The main remaining gap is that return shapes for list, invites, and plan are only implied rather than described.

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 100% and each parameter already documents its action mapping (e.g., invite_id for accept/decline). The description's action-to-parameter mapping is useful orientation but largely repeats what the schema says, so the baseline 3 is appropriate.

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 names the resource (family groups, members, invites, plan) and enumerates every action with the parameters each one takes. It explicitly routes recipe sharing to the sibling tool share_with_family, so the boundary 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?

It splits read actions from write actions, states which writes require asking the user first, and names share_with_family as the alternative for a related but different task. An agent can choose the correct action and know when confirmation is mandatory without opening the schema.

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