get_household_members

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

With no annotations, the description carries the full burden of behavioral disclosure. It notes the tool returns all users of the current household (a useful scope statement implying read-only), but says nothing about authentication requirements, pagination behavior despite seven paging params, or rate limits. A significant gap for an unannotated tool.

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 core purpose sentence and endpoint are reasonably front-loaded, but the trailing keyword block ('get_household_members, get household members, list member...') is a large volume of redundant filler that does not earn its place.

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 seven-parameter, zero-coverage, no-output-schema tool, the description is too thin: it does not document paging, ordering, or filtering behavior, and no output schema exists to compensate. An agent can identify the tool but not invoke it richly.

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 adds no meaning for any of the seven parameters (page, orderBy, perPage, queryFilter, orderDirection, paginationSeed, orderByNullPosition). 'Returns all users' does not explain any of these paging/filtering controls.

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?

States a clear verb (Get/List) and resource (household members), and the phrase 'current household' plus the endpoint [GET /api/households/members] scopes it enough to separate it from siblings like get_group_members or get_all_households. It is specific but does not explicitly contrast itself with those alternatives.

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 articulation of when to use this tool versus alternatives such as get_group_members, get_household, or get_logged_in_user_household. Usage is only implied by the resource name; the keyword list mentions 'search/find/browse' but provides no actual conditions or exclusions.

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