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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered. The description adds real context beyond them: the data is pre-existing and provider-reported, results are bounded, and it explicitly disclaims import/monitoring/attribution inference, which is valuable for an agent avoiding overreach.

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 tight sentences: purpose/scope front-loaded, then return fields, then explicit exclusions. Every clause carries information and nothing is wasted.

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 the return-field enumeration is a bonus rather than a necessity, and annotations cover the safety profile. The remaining gap is parameter semantics for a six-required-param tool with zero schema descriptions, which the description does not fill.

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% across six required parameters (workspaceId, platform, range, limit, offset, search), so the description must compensate but does not. It mentions the workspace conceptually and ordering by views, but says nothing about the platform/range enums, paging via limit/offset, or the search filter, leaving most parameters 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?

States a specific verb (Read) plus resource (existing provider-reported engagement), scope (in the selected workspace), and ordering (sorted by views), and even enumerates the returned fields. This clearly separates it from the editorial/generation siblings, none of which are read-only analytics tools.

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 negative constraints (does not import new data, start monitoring, or infer leads/sales/revenue) usefully bound what the tool is for, but there is no positive when-to-use statement and no named alternative sibling to route between. Usage is implied rather than stated.

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