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

Annotations already establish readOnly, idempotent, non-destructive semantics, so the safety profile is covered. The description adds useful behavioral context not in the annotations: that no scan is initiated, which is exactly the side-effect an agent might worry about here.

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 short sentences, scope stated first and the important negative constraint second. No filler.

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-value explanation is not needed, and the description hints at the payload ('latest saved profile/brief metadata'). Adequate for a single-param read tool; only slightly thin on the brandId parameter.

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%, and the single required 'brandId' is only implied by 'for this brand'. The description conveys that the result set is scoped to one brand, which adds meaning beyond the bare pattern, but gives no format or semantics detail.

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') and resource ('tracked public sources and their latest saved profile/brief metadata') scoped to a brand. It also implicitly distinguishes itself from scan_intelligence_target by clarifying it does not trigger a scan, though it does not name that sibling outright.

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?

Provides a clear exclusion ('Does not start a scan'), which routes the agent away from the scan variant for read-only listing. It lacks an explicit 'use scan_intelligence_target instead when you want to refresh' statement, so it stops short of the top score.

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