Ownership filings

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

Annotations already indicate that the tool is read-only (readOnlyHint=true) and open-world (openWorldHint=true), so the description does not need to repeat that. It adds the specific filing type but omits details like pagination behavior or data freshness. Given the annotations, the description minimally adds value beyond them.

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 a single sentence with no extraneous words, achieving high conciseness. It could be slightly more structured to include an action verb, but it is efficiently short.

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 description does not mention that the tool returns a paginated list (implied by cursor and limit parameters) or describe the output format. With no output schema, the agent lacks crucial information about what to expect. It also omits that ticker is for US equities, leaving room for misinterpretation.

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 100%, so all four parameters are already explained in the input schema. The tool description does not add any extra meaning or context for the parameters, thus it meets the baseline for this dimension.

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 explicitly states 'Schedule 13D/13G beneficial-ownership filings,' which clearly identifies the tool's purpose and distinguishes it from sibling tools like 'filers_holdings' or 'stocks_insiders.' However, it does not include a verb like 'list' or 'get,' leaving the action implied.

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 guidance is provided on when to use this tool versus alternatives. Sibling tools such as 'filers_holdings' or 'stocks_insiders' could be used for similar ownership data, but the description offers no comparative context or usage rules.

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