skylight_get_household_config

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

The description implies a read-only, non-destructive operation ('Get'), which is appropriate. With no annotations, it would benefit from explicitly stating that it does not modify any state. However, for a simple GET, this is minimally acceptable. No mention of authentication or rate limits, but those are not critical here.

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 very short at 8 words, which is concise but at the expense of necessary detail. It is front-loaded but lacks additional information that could be added without losing brevity. It earns a medium score because undue brevity reduces utility.

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 only one parameter, the description fails to explain the return format, what 'household configuration' includes, or how the parameter affects the response. The tool is relatively simple, but the description is insufficient for an agent to fully understand its behavior without external knowledge.

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 input schema has one parameter ('frameId') with no description, and the description does not explain its meaning or usage. With 0% schema description coverage and no parameter context in the description, the agent has no guidance on how to populate 'frameId' or what values are valid.

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' with context 'for the frame'. It effectively distinguishes from sibling 'skylight_update_household_config' as a read operation. However, it doesn't elaborate on what 'household configuration' entails, which could be more specific.

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 on when to use versus alternatives. While the sibling list includes an update counterpart, the description provides no context on prerequisites, typical use cases, or when to prefer this tool over other 'get' tools. The implied usage is simply when you need configuration data, but that is not explicit.

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