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

Annotations already declare readOnly=true, idempotent=true, destructive=false and closed-world, so the safety profile is covered. The description adds only 'interactive' and the notion of a time window; it says nothing about pagination (cursor), result limits, or how filters combine, leaving the behavior of a 15-parameter read largely undisclosed.

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 well-formed sentence with the view modes front-loaded and zero filler. It is efficient, though its brevity reflects under-specification rather than tight editing.

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 15 parameters, one required, no output schema, no parameter descriptions and no annotations gap to lean on, the description is far too thin. An agent cannot tell which optional filters to supply, how to paginate, or how this renderer differs from the read_visibility_* siblings.

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% with 15 parameters, so the description must compensate and largely does not. It gestures at three (view modes), the window (from_at/to_at) and one run (audit_id/snapshot_id), but level, limit, cohort, cursor, domain, engine, competitor, project_id, transport_model and retrieval_enabled receive no explanation at all.

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 concrete verb+resource ('Show an interactive visibility view') and enumerates its three modes (overview, trends, sources), which maps directly to the view enum. However, it does not distinguish this tool from siblings read_visibility_overview, read_visibility_trends and read_visibility_sources, which appear to cover the same ground; the render-vs-read distinction is left implicit in the word 'interactive'.

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 explicit when-to-use guidance, no prerequisites, and no comparison against the four read_visibility_* siblings that overlap with each view mode. The phrase 'for one run' weakly hints at scoping via audit_id/snapshot_id but is never tied to a parameter or condition.

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