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

Annotations already declare read-only, idempotent, closed-world, and non-destructive behavior. The description adds that results include 'explicit denominator and sample limits', which hints at data scope, but these terms are vague and not explained. No return format or pagination behavior is described.

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?

The description is a single compact phrase with no fluff, but it is too terse to be structurally helpful. It front-loads the core resource but omits necessary qualifiers about usage and behavior.

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?

With seven parameters, low schema coverage, no output schema, and only basic safety annotations, the description is incomplete for correct invocation. An agent lacks guidance on temporal scoping, filtering, pagination, or what the saved results actually contain.

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 only 29%; only 'url' and 'workspace' are documented in the schema. The description does not mention parameters like area, days, limit, offset, or direction, nor does it clarify how '30-day' relates to the days parameter. An agent must rely on sparse schema metadata for critical controls.

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 resource ('answer-engine visibility and competitors') and notes it is saved and 30-day scoped. However, it does not distinguish this tool from near-siblings such as read_brand_overview or read_visibility, so an agent cannot confidently select it over those without opening schemas.

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 guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The only implied context is that results are 'saved' and '30-day', which leaves selection largely to inference.

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