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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context that is not in the annotations: no provider contact and no credit consumption, which matters for cost-aware tool selection.

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 followed immediately by the cost/behavior caveat. Every clause earns its place with 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 values need no explanation, and the read-only annotations mean the description does not have to restate safety. What remains thin is sibling differentiation from list_intelligence_targets and any hint about which saved-item set is returned, but for a one-parameter read tool this is close to complete.

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?

There is only one required parameter (brandId) and schema description coverage is 0%, so the description carries the burden. "This brand's" implies the parameter identifies the brand whose saved items are read, but no format, source of the ID, or lookup hint is provided beyond the schema's regex pattern.

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?

"Read this brand's saved public evidence and notes" gives a clear verb (Read) and a specific resource (saved evidence/notes scoped to a brand). It is distinguishable from write siblings like save_intelligence_item and delete_intelligence_saved, but it does not explicitly separate itself from list_intelligence_targets or get_intelligence_scan, which are the closest siblings.

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?

"Does not contact providers or spend credits" implicitly signals when to prefer this over credit-consuming tools such as scan_intelligence_target, which is useful routing context. However, no alternative is named and no explicit when-to-use/when-not guidance is given.

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