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

Annotations already establish readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuinely new context: cursor-based paging, the data-quality caveat that missing metrics mean unknown rather than zero, and the guarantee that the source is not re-fetched. It stops short of stating result size limits or auth requirements.

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?

Three terse sentences, front-loaded with the core read semantics, with the pagination and data-quality caveats packed into a single clause each. No filler or restatement of the name.

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 an output schema present, return-shape explanation is unnecessary, and the description covers the read contract, paging, staleness behavior, and a meaningful data caveat. The main omission is any parameter guidance for the six undocumented optional inputs, which matters for a tool with this many knobs.

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 8 parameters, so the description must carry the load. It only touches pagination (nextCursor) and says nothing about days, sort, limit, scanId, search, or how brandId/targetId scope the read. The enums and defaults in the schema are self-documenting, which softens the gap slightly but does not fill it.

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?

Names a specific verb (Read) and resource (a tracked source's saved content, metrics and brief), which is far more precise than the sibling list_intelligence_targets. The closing clause 'Does not refresh the source' implicitly separates it from scan_intelligence_target, but no sibling is named outright, so an agent must still infer the boundary.

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?

'Follow nextCursor' gives a concrete procedural cue for continuing, and 'does not refresh the source' hints that a scan tool is the alternative when fresh data is needed. However, no explicit when-to-use/when-not or named alternative is stated, so usage is only implied.

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