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

Beyond the read-only and idempotent annotations, the description adds critical behavioral context: results are informational, read automatically from public filings, may contain errors, and must always include the source link. It also explicitly states never to present results as personal investment advice. This is valuable disclosure that the annotations alone do not provide.

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 long sentence that packs many details (targeting, actions, costs, borrowing, size, holdings, as-of dates, links, error disclaimer). It front-loads the core purpose and then lists specifics, but the run-on structure could be split into two sentences for clarity. Still, it is efficient and avoids redundancy.

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 tool with no output schema, the description fully explains what the agent can expect: the types of information returned (targeting, action items, costs, etc.) and the presence of as-of dates and source links. It also warns about potential errors and usage requirements, making it complete 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?

The schema already documents the single parameter ticker fully (including the hint to use search_funds when only the name is known). The description adds no additional parameter-level detail. Since schema coverage is 100%, a baseline of 3 is appropriate.

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 what the tool does: it tells the user about a large investor targeting a U.S. closed-end fund, action items, costs, leverage, size, and holdings, all sourced from SEC filings with as-of dates and links. It distinguishes itself from siblings like get_fund_holdings and get_fund_events by offering a comprehensive single-fund overview.

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 that this is the go-to tool for a full fund snapshot, but it does not explicitly state when to choose it over alternatives such as get_fund_holdings or get_fund_events. It also does not mention exclusions (e.g., 'use get_fund_holdings if you only need holdings'). The schema for ticker does hint to use search_funds for name-only lookups, but that guidance is not in the description itself.

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