households_event_notifications_get_all

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

With no annotations, the description carries the full burden. The keyword 'read-only' gives a weak hint that this is a safe read, but nothing explains pagination scoping, default page size, ordering defaults, or authorization requirements — notable gaps for a tool exposing seven pagination/ordering parameters.

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 opening two lines are tight and front-loaded, but the appended keyword list is pure noise that pads the definition without adding selection or invocation value. The signal is buried in repetition.

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 output schema, and no annotations, the description is markedly incomplete. It never addresses pagination behavior or ordering, which are the core concerns of calling this tool 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?

Schema description coverage is 0% across seven parameters (page, perPage, orderBy, orderDirection, queryFilter, paginationSeed, orderByNullPosition), and the description explains none of them. The keyword 'search notification' hints that queryFilter exists but gives no syntax or semantics, so the description does not compensate for the coverage 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 states a specific verb and resource: 'List notifications' for household event notifications, and the 'Get All' prefix signals the collection-level variant against siblings like households_event_notifications_get_one. However, the bulk of the text is a keyword dump that adds no additional distinguishing information, so it stops short of 5.

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 explicit when-to-use statement, no prerequisites, and no routing to alternatives beyond the implicit list-vs-single distinction in the name. An agent must infer that this is the collection fetch rather than one of the create/get_one/update/delete siblings.

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