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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions pagination and that it is a summary, but does not explain the scope of 'days', how filtering or locale affect results, or what the response structure looks like. No side effects are stated, though none are expected for a read operation.

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 concise and front-loaded, with no filler. The two sentences each add information, though 'etc.' is vague and could be replaced with more concrete examples or scope details.

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 five parameters, no output schema, no annotations, and many sibling tools, the description is too sparse. It does not explain return values, the meaning of days, filter syntax, locale behavior, or how this tool differs from get_us_corp_actions.

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 for the five parameters. It only hints at pagination, leaving days, filter, locale, and page_size semantics unexplained. This is a significant gap for an agent trying to invoke the tool correctly.

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 clearly identifies the resource as corporate actions and gives concrete examples (buybacks, dividends, placements). It is unambiguous about what the tool returns, though it does not differentiate itself from sibling get_us_corp_actions or other corporate-action-related tools.

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?

There is no guidance on when to use this tool versus alternatives such as get_us_corp_actions, get_buyback_ranking, or get_stock_buyback. The description only states what it returns, not when it should be selected.

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