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

With no annotations, the description carries the full burden. It usefully discloses that holdings reflect disclosure dates rather than today and gives a concrete pagination protocol (top-level page, keep filters unchanged, pass next_cursor verbatim). It omits other behavioral traits like authentication or rate limits, but covers the most operationally important caveats.

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 first sentence states purpose and pagination; the next two add critical caveats. There is no redundant or filler text, and the information is front-loaded.

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 tool with no annotations and no output schema, the description covers what data is returned and how to paginate, but it does not describe the response shape or provide usage guidance against siblings. It is adequate but leaves clear gaps.

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 fully documents all four parameters, setting a baseline of 3. The description adds a meaningful pagination rule for cursor and filters (keep filters unchanged and pass next_cursor verbatim), which goes beyond the schema's static descriptions.

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 the exact resource (disclosed fund holdings and portfolio weights) with a clear verb. It does not reference any sibling tool (e.g., get_shareholders_latest) to help an agent disambiguate, so it stops short of the top score.

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?

It explains pagination mechanics but never states when this tool should be chosen over other holdings or shareholder endpoints. There are no exclusions, prerequisites, or alternative-tool references.

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