skylight_get_frame

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

The annotations already declare readOnlyHint=true, and the description's 'Get' is consistent with a read-only operation. The phrase 'and its settings' adds a little context about the payload scope, but it does not disclose additional behaviors such as auth requirements, error cases, or what happens when frameId is omitted beyond what the schema already states.

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 one short, front-loaded sentence with no filler. Every word contributes to identifying the resource and the operation, making it appropriately concise.

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 tool's simplicity — one optional parameter, no nested objects, and a read-only annotation — the description is nearly complete for invocation. It could be slightly more explicit about what the returned settings include and how this relates to skylight_list_frames, but the schema and sibling context cover most of the remaining ambiguity.

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?

Schema description coverage is 100%, and the frameId parameter already has a helpful description including the resolved-frame default. The tool description adds no additional parameter-level meaning, so the baseline score of 3 is appropriate.

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 the verb 'Get' with a specific resource: 'one Skylight frame and its settings.' The singular 'one' distinguishes it from sibling tools like skylight_list_frames (enumeration) and skylight_update_frame (mutation), so an agent can identify the intended operation clearly.

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?

The singular 'Get one' implies this tool is for retrieving a single frame's settings, but the description gives no explicit when-to-use or when-not-to-use guidance. It does not mention alternatives such as skylight_list_frames or explain when to rely on the resolved-frame default, leaving the selection largely to inference.

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