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

With no annotations, the description carries the full burden. It does not disclose whether the refresh is idempotent, what happens if no live preview session exists, whether it requires a running capture job, or what the frame/response looks like. 'Force' hints at overriding caching but is never explained.

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 short, front-loaded sentence with zero padding. It is efficient, though its brevity borders on under-specification rather than economical phrasing.

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 tool with no annotations and no output schema, the description says nothing about side effects, failure behavior, or relationship to sibling preview tools. The required captureJobId is undocumented in the prose, and an agent has no picture of what a successful call yields.

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%, with captureJobId documented as 'cap_*' format and notification_message explained in the schema, so the baseline is 3. The description adds no parameter guidance of its own, but nothing is missing.

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+resource: 'Force refresh live PNG frame.' An agent can tell it forces a re-render of a live preview frame. It does not, however, distinguish it from the sibling open_live_preview, which reads as the same resource.

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 indication of when to use this versus open_live_preview, no prerequisites, and no note on whether the preview need already be open. The agent must infer all routing decisions from the name alone.

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