Load one exact preview for confirmation

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

Adds context beyond annotations: app-only scope, returns image bytes only to the component, and issues session-bound confirmation challenge. Read-only hint already covers safety, so description enriches the behavioral model without contradiction.

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?

Two short sentences, front-loaded with the core scope. No filler words; every clause contributes meaning.

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?

Despite having no output schema and no param descriptions, the description does not clarify the confirmation challenge workflow or the exactSelector object structure. It covers return behavior but leaves operational details ambiguous.

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 coverage is 0%, yet description does not explain providerId, resultSetId, or exactSelector structure. The word 'exact' loosely maps to exactSelector but no concrete syntax or semantics are provided.

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?

Clearly states it is an app-only exact preview that returns image bytes and issues a session-bound confirmation challenge. Distinguishes from headless preview and confirmation tools by emphasizing app-only and confirmation challenge.

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?

Implies usage context through 'App-only' and 'session-bound confirmation challenge' but does not explicitly name alternatives or state when-not-to-use. No explicit exclusion of headless variants.

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