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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety bar is largely met. The description adds real value by clarifying the side-effect boundary ('Does not start a scan') and stating what the returned metadata actually is (latest saved profile/brief), which annotations do not convey.

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, front-loaded with the core action and then the semantic boundary, with no filler. Slightly clipped wording ('for this brand' is a bit loose), but every clause earns its place.

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 shape need not be described. For a single-parameter, read-only list tool the description covers purpose, scope, and the key scan/no-scan distinction; only the relationship to the other intelligence siblings remains unstated.

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% for the single brandId parameter. The phrase 'for this brand' loosely ties the input to a brand but adds no format, ID-style, or constraint detail beyond what the schema's pattern already encodes. Only marginal meaning is added over the schema.

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 concrete verb+resource ('read tracked public sources and their latest saved profile/brief metadata') scoped to a brand, and the closing 'Does not start a scan' distinguishes it from scan_intelligence_target. It does not name get_intelligence_target or list_intelligence_saved, so sibling differentiation is partial rather than explicit.

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 negation 'Does not start a scan' implicitly routes the agent away from the scan sibling, which is useful. However there is no positive when-to-use guidance and no mention of how this differs from get_intelligence_target (single) or list_intelligence_saved, leaving the choice only implied by the 'list' name.

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