skylight_update_frame

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

The description only states 'Update', implying mutation, but no annotations are provided. It fails to disclose behavioral traits such as required permissions, idempotency, side effects (e.g., changes take effect immediately?), or rate limits. The description carries the full burden and does not meet it.

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 (6 words), which is efficient but insufficient for an 11-parameter tool. It is not verbose, but the lack of detail makes it merely adequate rather than well-structured.

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?

Given the complexity (11 parameters, no output schema, no annotations), the description is grossly incomplete. It does not explain return values, constraints, or the effect of missing parameters, making it insufficient for correct invocation.

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?

With only 9% schema description coverage (one out of 11 parameters has a description in the schema), the tool description adds no parameter information. It does not compensate for the low coverage, providing no additional meaning beyond the raw schema.

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 uses a specific verb ('Update') and resource ('Skylight frame'), and clearly distinguishes from sibling tools like skylight_list_frames or skylight_get_frame by indicating it modifies settings. While 'display/sleep' is slightly vague relative to the full parameter set, the overall purpose is unambiguous.

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 this tool versus alternatives (e.g., skylight_rename_frame). There is no mention of prerequisites, contexts, or exclusions, leaving the agent without decision support.

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