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

Annotations already mark the tool read-only and idempotent, so the description is not needed for that. It adds valuable behavioral context by warning that results are informational, 'may contain errors,' and should always be presented with the source link and never as personal investment advice.

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 compact and front-loads the core purpose, then adds essential caveats in the second sentence. The parenthetical list of event types is slightly dense but still serves to clarify scope without waste.

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 compensates by specifying what results contain: event types, deadlines, actions, as-of dates, and source links. It also covers the reliability caveat and the required presentation behavior, making the tool fully understandable for selection and invocation.

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%, with both 'ticker' and 'months' already described, including defaults and an example. The description does not add parameter-level meaning beyond the schema, so the baseline score of 3 is appropriate.

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 and resource: 'Lists one closed-end fund's dated announcements' and enumerates concrete event types such as buyback offers, shareholder votes, and mergers. This clearly distinguishes it from sibling tools that cover holdings, fund profiles, or general events.

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 description makes the intended use clear: it is for announcements 'a holder may need to act on,' with deadlines and instructions, sourced from SEC filings. It does not explicitly name alternatives or exclusions, but the singular 'one closed-end fund's' scope provides enough contextual routing for an agent.

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