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

The readOnlyHint and openWorldHint annotations already establish that this is a safe, open-world data retrieval operation. The description adds that results are top positions by USD value and cites SEC Form 13F as the source, but it does not clarify how many positions are returned, which reporting period is used, or whether only the latest filing is covered.

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 two short sentences with no wasted wording. The core data scope is front-loaded, and the source attribution is compact.

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 one-parameter retrieval tool, the definition covers the essential data type and identifier. However, it leaves open important context such as filing period, number of top positions, and whether the result is based on the latest Form 13F only, which is meaningful for an agent invoking a financial holdings tool.

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 sole parameter rssd_id is fully documented in the schema as a Federal Reserve RSSD id, and the description's reference to a bank's holdings reinforces that the identifier selects a bank. However, the description adds no further meaning about identifier resolution or edge cases beyond what the schema already provides.

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 identifies the resource as a bank's institutional-manager Form 13F holdings and specifies that it returns top positions by USD value. It is specific enough to distinguish the data type, though it does not explicitly differentiate this tool from nearby SEC filing tools such as sec_13dg or sec_filings.

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 resource name and the mention of institutional-manager Form 13F holdings, but there is no explicit guidance on when to choose this tool over related SEC tools. The agent can infer the use case, but no alternatives or exclusions are provided.

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