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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that no work starts and that it reads saved build options plus mockup references, but it does not describe pagination, scope behavior, or return characteristics.

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, with the purpose front-loaded and no wasted wording. The second sentence reinforces the read-only/no-side-effect nature efficiently.

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 an 8-parameter tool with no schema descriptions and no output schema, the description is too sparse. It does not compensate for the missing parameter documentation or explain what a caller should expect to retrieve.

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 schema has 8 parameters with 0% description coverage, and the description explains none of them. Terms like "saved report" hint at report_id, but workspace, scope, limit, offset, glowup_ref, recommendation_id, and prospect_session_id are left entirely undocumented.

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 names a specific read operation on saved report build options and mockup references. It is clear enough to understand the resource, but it does not explicitly distinguish this tool from siblings such as glowups_get, glowup_build_open, or glowup_attach.

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 work starts" implies this is a safe inspection call rather than a build or attach action, which gives some usage context. However, it does not explicitly state when to use this instead of related GlowUp tools or what prerequisites are required.

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