households_webhooks_get_all

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read-only list via keywords, but says nothing about pagination (despite page/perPage params), permissions, ordering defaults, or the shape of results. A network list endpoint with seven params deserves more disclosure.

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 useful content ('Get All — Households: Webhooks. List webhooks.' plus the endpoint) is front-loaded, but it is followed by a long, redundant keyword list that repeats the same terms repeatedly without adding information.

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 list endpoint with seven undocumented parameters, no annotations, and no output schema, the description should at least describe pagination and filtering behavior. It gives only the route and a keyword blob, leaving the agent unequipped to call it correctly.

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 schema has 7 parameters with 0% description coverage, and the description supplies no meaning for any of them (page, orderBy, perPage, queryFilter, orderDirection, paginationSeed, orderByNullPosition). It neither explains the query filter syntax nor the ordering semantics, so the heavy compensation requirement is unmet.

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 states a clear verb and resource ('List webhooks' scoped to Households) plus the underlying endpoint GET /api/households/webhooks. It is distinguishable from the get_one sibling since it is explicitly a list operation. It does not, however, explicitly contrast itself with households_webhooks_get_one.

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 statement of when to use this tool versus alternatives such as households_webhooks_get_one or the other households_* list endpoints. The only routing aid is a keyword dump, which names no conditions or exclusions.

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