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

Annotations already carry the full safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds useful content scope (what categories of data come back) and 'latest' hints at freshness, but it says nothing about what happens for an untracked or unknown fund, or how stale a 13F can be.

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?

One densely packed sentence with the resource and the three returned data categories front-loaded; no filler, no restatement of the name or title.

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 one-parameter, read-only, no-output-schema tool, the description usefully previews the return shape (current positions, deltas, exits), which is exactly what's missing without an output schema. Only the error/freshness behavior for untracked funds is left uncovered.

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% and the single 'fund' parameter is documented with an example, so the schema does the work. The description only echoes the constraint via 'a tracked fund's' and adds no format or resolution detail beyond it.

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 names a specific resource (a tracked fund's latest 13F) and enumerates the payload: positions with shares and reported value, quarter-over-quarter changes, and exits. That is enough to separate it from list_funds or get_company in practice, though it never explicitly contrasts itself with those siblings.

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 qualifier 'a tracked fund's' implicitly signals that the fund must already be tracked (presumably discoverable via list_funds), which is a useful but unstated constraint. There is no explicit when-to-use/when-not guidance and no named alternative for related needs.

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