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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuine behavioral value by enumerating the returned facets and disclosing a concrete limitation ("Physical DPI is unknown"), which an agent can use to avoid assuming DPI availability. It says nothing about the required control token or auth expectations, keeping it short of a 5.

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?

A single front-loaded sentence with no filler; the return contents lead and the DPI caveat trails appropriately. Dense enumeration of six payload facets pushes it toward a list, but nothing is wasted.

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?

For a read-only tool with no output schema, describing the returned facets is the right move and mostly done. However, the one required parameter is undocumented and there is no guidance on when this read is appropriate, leaving an agent able to understand the payload but not fully equipped to invoke it.

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 single required parameter controlToken has 0% schema description coverage, so the schema contributes no meaning at all. The description never mentions the token, its origin, or what it authorizes, leaving the caller without the information needed to supply it correctly.

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?

States a specific verb ("Reads") plus the exact payload it retrieves: workspace revision, focus, component summaries, render status, media capabilities, display dimensions. That is far more informative than a restatement of the name. It does not, however, explicitly distinguish itself from siblings such as read_component or claim_canvas, so an agent must infer the boundary.

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 statement of when to call this versus alternatives like read_component, claim_canvas, or get_console, nor any prerequisite guidance. Usage is only loosely implied by the read-only nature of the payload.

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