A tracked manager's 13F portfolio

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

With no annotations, the description carries the full burden, and it partially delivers: it discloses that data is 'latest' 13F (quarterly filing cadence, snapshot in time) and describes the payload contents (value, shares, share of portfolio). It omits any statement of auth requirements, rate limits, or whether non-tracked managers return empty/error responses.

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?

Two tight sentences with no filler; the resource scope is front-loaded before the example slugs and the return-field note. The examples list is slightly redundant with the schema, keeping it just short of ideal.

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 single-parameter lookup with no output schema, the description supplies both the identifier convention and the shape of the returned positions, which is what an agent needs to call and interpret it. Missing usage routing against siblings is the main gap.

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% and the schema already documents the slug parameter with an example. The description reinforces the slug semantics with additional example slugs, but adds no format rules or constraints beyond what the schema provides, so the baseline of 3 applies.

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 scope: the latest 13F portfolio of one tracked manager, identified by slug. It provides concrete example slugs (berkshire-hathaway, bridgewater, citadel-advisors, renaissance-technologies), making the resource unambiguous. It is clear but does not explicitly name or differentiate itself from nearby siblings like fund_holders or large_holders.

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 implies the tool is for retrieving a specific tracked manager's holdings, but it never states when to use this versus fund_holders, large_holders, or insider_trades. No exclusions, prerequisites, or alternative-selection guidance are given.

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