Read complete design context

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does state what is returned and frames the purpose, and the title indicates a read operation. However, it does not disclose side effects, authorization needs, defaults, or caveats around generating target code.

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 that names the returned artifacts and the reason for using the tool. There is no filler, repetition, or unnecessary detail.

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 five parameters, no annotations, no output schema, and closely related sibling tools, one sentence is not enough. It omits parameter interactions such as selection vs. screen, output shape, and when to choose this combined tool over the more granular siblings.

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 0%, so the description needed to compensate. It only implicitly hints at 'target' via 'target code' and 'includeVisual' via 'visual PNG'; host, scope, and screenId are left unexplained, leaving the agent to guess how parameters relate.

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 ('Return') and names the exact contents: design properties, a visual PNG, and generated target code. This bundle clearly distinguishes the tool from narrower siblings like get_selection_context, get_visual_context, and generate_code.

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 description gives a clear usage context: use this tool when an agent needs structure, appearance, and implementation together. It does not explicitly name alternatives or exclusions, but the stated rationale is strong enough to signal when this combined read is appropriate.

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