finance.thirteen-f

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

Discloses that market values are converted from the SEC's $000s convention, and notes sorting by value descending. No annotations exist, so description covers key behavioral traits.

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?

Single paragraph covers all essential information without waste: purpose, output fields, sorting, parameter hints, and example CIKs. Every sentence adds value.

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?

Thoroughly explains return fields and gives parameter examples. Lacks mention of error conditions or missing data scenarios, but is adequate given the tool's simplicity and lack of output schema.

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?

Adds meaning beyond schema by explaining limit sorts descending, formType variants (HR/A, NT), and CIK format. Schema coverage is 100%, but description enhances each parameter with practical context.

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 states the tool returns parsed institutional holdings (Form 13F-HR) for a CIK, listing specific fields. It distinguishes from sibling finance tools by its unique focus on 13F filings.

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?

Provides example CIKs for common managers and explains parameters like formType variants. However, does not explicitly state when not to use it or mention alternatives among siblings.

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