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

Annotations declare readOnlyHint=false, destructiveHint=true, idempotentHint=false and openWorldHint=true. The description helpfully discloses the snapshot write and the public (open-world) URL, but leads with 'READ-only (+ stores a snapshot)', which is at odds with readOnlyHint=false, and never explains the destructiveHint=true implication (e.g. what an existing snapshot is replaced or what is overwritten). The tension is compounded by an unexplained destructive flag.

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?

Front-loaded with the key differentiator (public shareable link) and compact. Some redundancy in the all-caps framing and the trailing 'READ-only (+ stores a snapshot)' clause dilutes rather than informs.

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?

An output schema exists, so return values need not be explained. However, for a tool with a hidden write side effect (snapshot storage, destructive flag) and zero parameter documentation, the description leaves important operational context unstated.

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% for three parameters. The description only clarifies one: brand_name appears in the report title. Neither `days` (default 30) nor `customer_id` (required) is given any meaning, so the description does not compensate for the empty schema.

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 concrete verb+resource combination: it generates client_report, freezes a snapshot, and returns a public URL. This is clearly distinct in output shape from the sibling `client_report`, though the description never names that sibling to draw the contrast explicitly.

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 phrase 'a page URL you can send to your client' implies the use case (client-facing deliverable), but there is no explicit when-to-use/when-not guidance and no routing away from the closely related `client_report` sibling. Usage must be inferred.

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