Ownership filings

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds ordering behavior ('most recent first') and pagination behavior (cursor/limit or auto-collect with max_items). This provides useful context beyond annotations, though it does not detail rate limits or maximum page sizes beyond schema constraints.

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?

Three concise sentences: first defines the core function, second explains pagination, third provides alternatives. No redundant information, front-loaded with the most important action.

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 the absence of an output schema and the tool's moderate complexity, the description fully covers what the tool does, how to use pagination, and when to use sibling tools. No gaps in essential information.

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 coverage is 100% with parameter descriptions. The description adds value by explaining how max_items enables auto-collect across pages, which is not detailed in the schema. This enhances understanding of the parameter's behavior beyond the basic description.

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 specifies the exact resource (Schedule 13D/13G beneficial-ownership filings), the action (list), and ordering (most recent first). It clearly distinguishes from sibling tools stocks_insiders and filers_holdings by specifying their different use cases.

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?

The description explicitly provides alternatives for related tasks: 'For officer/director trades use stocks_insiders; for institutional 13F positions use filers_holdings.' It also explains pagination options (cursor/limit vs. max_items), giving clear guidance on when to use each.

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