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

Annotations already mark the tool as read-only, idempotent, open-world, and non-destructive. The description adds useful interpretive context by stating that the data is current monitoring, not historical evidence, and by flagging source failures and limitations, which aligns with the open-world hint. No contradiction with the annotations exists.

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?

The description is short and front-loaded, with each sentence contributing a distinct fact: the tool's scope, the fields to preserve, usage exclusions, and argument restriction. There is no filler or redundant restatement of schema or annotations.

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?

Given that an output schema exists and the annotations cover safety, the description covers the essential selection and invocation concerns: it identifies what the tool monitors, tells the agent when not to use the result, and states the single input. The cryptic 'preserve scan versus review clocks' phrase is the main gap, but the output schema can resolve field-level meaning.

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?

With 0% schema description coverage, the description must define the parameter itself. It does clarify that the only argument is a ticker and that no other arguments are accepted, but it does not provide a format, example, or further constraints beyond the schema's 'symbol' property.

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?

The description identifies the tool's subject as 'current monitoring' and distinguishes it from the 'immutable company file,' narrowing scope to live research status rather than historical data. It names the content areas (scan versus review clocks, pending leads, source failures, limitations), though it lacks an explicit verb and relies on the tool name/title to convey the retrieval action.

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?

It gives clear negative guidance: current monitoring must not be used as historical evidence or as approval to promote a company, and it should be used alongside the immutable company file. However, it never names the sibling tool that should be preferred for historical evidence, so the routing is implied rather than explicit.

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