get_announcements

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

With no annotations, the description carries the full burden. It does disclose useful behavior beyond the schema: results are ordered newest first and each item contains a date, title, and optional PDF link. It omits permission requirements, pagination/limit behavior, and how far back 'recent' extends.

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 purpose and followed by the return shape. No wasted words, though the line breaks make it slightly less clean than a single sentence would be.

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?

The low-complexity surface (2 params, no output schema) means output field disclosure is helpful and mostly sufficient. However, with zero schema coverage on the parameters, the description leaves the required-call contract incomplete.

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 0%, so the description must compensate, but it says nothing about the required `symbol` parameter or the `limit` control. An agent cannot tell from the description that a ticker symbol scopes the announcements or that limit caps result count.

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+resource: retrieving recent corporate announcements for a symbol. It is clearly distinguishable from sibling tools like get_dividends or get_company_info, though it never explicitly says how it differs or which sibling to use for related data.

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?

No when-to-use guidance, no mention of when this is preferable to get_company_info or get_dividends, and no prerequisites. The agent must infer that this tool exists for announcement/regulatory disclosures only.

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