get_logged_in_user_household

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 discloses that this is a read operation via the GET route and the 'read-only' keyword, and says it returns household data for the current user. It does not clarify auth requirements, error behavior, or rate limits, which keeps it at a moderate rather than strong disclosure level.

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 information is front-loaded, but the description is bloated by a long keyword list that repeats synonyms such as 'get household self', 'fetch household self', and the individual verbs 'get, fetch, read, retrieve, view, show'. This keyword stuffing adds noise without decision value and makes the description poorly sized.

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 zero-parameter, read-only endpoint, the description supplies the route and summarizes the return as 'Household Data for the Current User'. No output schema exists, but the return content is described well enough. Auth is implied by 'Logged In User', though permissions are not explicitly confirmed.

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 tool has zero parameters and 100% schema description coverage on an empty schema. Per the rubric baseline for a 0-parameter tool, a 4 is appropriate. The description adds no parameter meaning because no parameters exist.

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: get the household belonging to the logged-in user. The 'self' and 'Current User' framing distinguishes it from siblings such as get_logged_in_user (user profile), get_one_household, and get_all_households (other household scopes). It is clear, though not elegantly phrased.

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?

Usage is implied through 'Self Service' and 'Current User', suggesting this is the correct tool when the caller wants the current user's own household. However, it does not explicitly state when to choose it over get_logged_in_user, get_logged_in_user_group, or get_household, nor does it give exclusions.

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