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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely valuable behavioral context beyond annotations: the partial-coverage caveat — 'an empty answer may be a coverage gap rather than corporate silence; the response says which case applies' — plus 'scraped from the company's IR website' hinting at an external dependency. This materially improves agent interpretation of empty results.

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 front-loaded with purpose and scope, then return format, then usage context, then the coverage caveat. Every sentence earns its place, though it is slightly verbose — the coverage disclosure could be tightened. Overall efficient and well-ordered.

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?

With no output schema, the description fills the gap by specifying returned fields (headline, publish date, summary, link) and ordering (reverse-chronological). It also covers the empty-answer ambiguity. For a 4-parameter read tool with one required param, nothing an agent needs to call it correctly 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 description coverage is 100%, so all four parameters (ticker, since, offset, maxResults) are already documented in the schema, which sets the baseline at 3. The description focuses on return format rather than parameter syntax and does not add meaning beyond the schema, which is acceptable given full coverage.

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 states a specific verb ('Get'), resource ('investor-relations press releases for a stock, scraped from the company's IR website'), and explicitly differentiates from third-party news. This distinguishes it from siblings like GetEarningsBrief and GetEarningsCallTranscript by content type, so an agent can select it confidently without opening schemas.

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?

'Use this to see a company's latest official announcements straight from its IR page, distinct from third-party news' gives clear context for when the tool is appropriate, distinguishing official IR releases from third-party coverage. It stops short of naming explicit sibling alternatives or stating when not to use it, but the intended use case is unambiguous.

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