List Households Webhooks

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get All' reveals nothing about read-only behavior, pagination, response structure, authentication, or side effects. The tool has a pagination-related parameter set, but the description does not even hint at these behaviors.

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 words are compact, but this is under-specification rather than efficient writing. The description does not earn its place because it conveys no useful information beyond what the name already implies. A well-structured description would include at least the resource scope and key behavior.

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 8 parameters, no annotations, and a large set of sibling list tools, the definition is severely incomplete. The output schema exists, so return values need not be explained, but the description still fails to clarify purpose, usage, filtering behavior, or any parameter semantics. An agent cannot reliably select or invoke this tool based on the provided definition.

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%, and the description names no parameters or their meaning. Parameter names like perPage, queryFilter, and orderBy provide hints, but the description adds zero value beyond the schema. With 8 undocumented parameters, this is a critical gap.

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 'Get All' is essentially a verb phrase that paraphrases the action implied by the tool name without naming the resource. It provides no specific statement like 'List all webhooks for a household', so an agent must infer meaning entirely from the tool name. This is close to a tautology and offers no distinction from many other 'list_' sibling tools.

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?

There is no guidance about when to use this tool versus alternatives such as get_households_webhooks_by_item or list_households_invitations. The description gives no context about pagination, filtering, or typical use cases. It is not misleading, but it provides no usage direction at all.

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