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

Annotations are absent, so the description carries the full behavioral burden. It does disclose pagination behavior and a market-wide scope, but it omits the ranking basis, the meaning of days, locale effects, and return format details. This is minimal useful disclosure, not comprehensive.

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 free of filler, with the pagination note earning its place. It is front-loaded and easy to scan, though the terseness contributes to semantic gaps elsewhere.

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 four parameters, no output schema, no annotations, and many similar ranking siblings, this description is under-specified. It does not explain ranking criteria, day-range semantics, locale behavior, or how this tool differs from get_stock_buyback and other ranking tools. An agent can call it, but choosing and interpreting it confidently is hard.

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. It explicitly explains page and page_size as pagination controls, but days and locale receive no explanation beyond their names and defaults. Partial value is added, but not enough for full confidence.

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 phrase 'Share buyback ranking across listed companies' clearly names the resource and scope, and the market-wide framing distinguishes it from per-stock buyback tools like get_stock_buyback. However, there is no explicit verb, so the description relies on the tool name for the 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?

No when-to-use guidance is provided, and there are no explicit exclusions or alternatives. Given many sibling ranking tools, the agent is left to infer when this tool is appropriate rather than being told directly.

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