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

With no annotations, the description carries the behavioral burden well: it discloses that filings are parsed per call and that the tool is pay-per-call at $0.002 USDC on Base, with a 402 challenge on unpaid calls. It does not cover error behavior, rate limits, or exact result-count limits, but the payment and freshness behavior are unusually transparent.

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 front-loaded: the first sentence names the tool's purpose and output, and the second adds source and payment behavior. Every clause contributes useful context without padding.

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?

For a simple two-parameter lookup with no output schema and no annotations, the description covers the data source, the returned fields, and the payment model. It leaves some ambiguity around identifier precedence, result limits, and failure cases, but it is largely sufficient for correct invocation.

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 the schema is the primary parameter reference. The description adds useful meaning by saying the investor may be identified by CIK or name and by clarifying that results are top 13F positions, but it does not explain whether one identifier is preferred or required when both are omitted or supplied.

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 states a specific resource and verb: latest SEC 13F holdings for an institutional investor by CIK or name. It also names the returned content (top positions with issuer, value, and share count), making the tool readily distinguishable from broader EDGAR or insider tools.

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?

Usage is implied by the 13F/institutional-holdings framing, but the description gives no explicit when-to-use or when-not-to-use guidance. It also does not route the agent to alternatives such as edgar_company or edgar_search when the task is not specifically 13F holdings.

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