get_beneficial_ownership

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds useful domain context by defining 13D/13G intent, but says nothing about result volume, ordering, or rate limits. With annotations carrying the behavioral load, this is adequate but thin.

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?

Purpose is front-loaded in a single sentence, followed by a compact Args/Returns block. The docstring-style formatting is slightly boilerplate but nothing is padded or redundant.

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?

An output schema exists, so return values need not be spelled out in detail. Purpose and all three parameters are documented, and the tool is a read-only fetch with no side effects to warn about. Only the missing when-to-use guidance against sibling tools keeps it from being fully complete.

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 is doing all the work, and it does it: ticker as the stock symbol, limit as the number of reports, and schedule with its default ('all') and the meaning of each option. Decent compensation, though it omits valid range or upper bound for limit.

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 and resource: 'Get beneficial ownership reports (13D, 13G) for a company.' That is enough for an agent to know it fetches ownership filings rather than holdings or insider trades. It stops short of explicitly distinguishing itself from nearby siblings like get_13f_holdings or get_insider_transactions.

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 when-to-use guidance, no prerequisites, and no named alternative. The parenthetical definitions of 13D (activist or control intent) and 13G (passive holder) explain the filing types but describe the parameter, not when an agent should pick this tool over a sibling.

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