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 profile is covered. The description still adds useful behavioral scope beyond that: a bounded result set (up to 12 findings), that findings carry dates and available links, and that leads include dated proof, which tells the agent what to expect from the call.

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 sentences, no waste. The output contents are front-loaded, input formats follow, and the scoping caveat lands last where it is most useful.

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?

For a single-parameter read tool with full annotation coverage, the description supplies what annotations and schema cannot: the shape and limits of the returned content. No output schema exists, yet return values are adequately characterized, so nothing essential is missing.

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 coverage is 100% and the single parameter's description ('Domain, company name, or account id') mirrors the description's text almost verbatim. The only added value is the concrete format example 'acme.com', so this sits at the baseline.

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 and resource (read saved context for one company) and enumerates the payload: recent findings with dates/links plus open leads with dated proof. The closing clause 'This does not run a new check' explicitly separates it from check-running siblings such as get_account_changes.

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?

Clearly gives the trigger context (account on your tracked list) and the accepted input forms (domain, company name, or id), plus the negative case that it does not perform a fresh check. It stops short of naming an alternative tool to use when a new check is actually wanted.

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