skylight_get_household_config

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

The readOnlyHint annotation already communicates the safety profile, and the description's 'Get' is consistent with it. The description adds only the target scope 'for the frame' but provides no behavioral details about defaults, response shape, or behavior when frameId is omitted.

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 front-loaded sentence with no filler. It is efficient, though it could carry more useful detail without becoming bloated.

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?

With no output schema and no parameter documentation, the description leaves important invocation details unstated: what the household configuration return object contains and whether frameId is optional or defaults to a specific frame. Given the large sibling set, this is thin context for reliable use.

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 provides only a bare frameId string with no description, and schema coverage is 0%. The phrase 'for the frame' loosely maps to frameId, but it does not explain whether the parameter is required, what it selects, or what happens if omitted. The description does not compensate for the schema 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 clearly states the verb 'Get' and the resource 'household configuration', scoped to 'the frame'. This distinguishes it from skylight_update_household_config. It loses a point because it does not specify what the household configuration actually contains.

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 guidance about when to use this tool versus alternatives such as skylight_get_frame or skylight_update_household_config. Usage is only implied by the getter semantics and resource name.

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