Household Get Household Member

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond the name: it does not mention output_mode behavior, field projection semantics, potential errors, or what 'get' returns. No contradiction exists, but the description contributes almost nothing beyond annotations.

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 description is a single short sentence and is not verbose, which is structurally clean. However, it is under-specified rather than efficiently informative; it conveys almost the same information as the title and leaves important operational details absent.

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 simple retrieval tool, the combination of name, schema, and annotations provides partial context, but the description itself is too thin. There is no output schema, no explanation of member_id semantics, no note distinguishing this from list/get siblings, and no coverage of how output_mode and fields affect the result. An agent would need to infer most operational detail from parameter names alone.

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 documents fields and output_mode with meaningful descriptions, providing 67% coverage. However, member_id, the only required parameter, has no description and the tool description does not explain its meaning or where to obtain it. The description also does not clarify how fields/output_mode interact with the returned member data.

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 the verb 'Get' and resource 'household member', so an agent can tell it retrieves a member. However, it is nearly identical to the tool name/title and does not clarify whether this fetches by ID or which member, nor does it distinguish it from sibling tools like household_get_current_user or household_list_household_members.

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?

No guidance is given on when to use this tool versus alternatives. The existence of household_list_household_members and household_get_current_user as siblings creates potential ambiguity, and the description does not mention that member_id is required or that this tool is for fetching a single member by identifier.

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