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

The description adds meaningful behavior beyond the readOnly/destructive annotations: it clarifies the metric is not total firm AUM, states possible fallback to filer values, notes zero can represent unavailable valuations, and explains the ambiguous-name behavior. This gives agents important expectations about output values and name resolution.

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 dense but efficient, front-loading the core purpose and output fields, then adding valuation caveats and name-resolution guidance. Every sentence contributes useful information, though the long first sentence is somewhat heavy for a quick scan.

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?

Without an output schema, the description compensates by enumerating the specific returned metrics and caveats about price sources and zero values. It also covers the key caller concern of name ambiguity. Minor gaps such as error behavior or pagination are not critical for a summary-header 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?

Schema coverage is 100%, so the parameters are already fully documented. The description adds some context around name matching ('ambiguous partials return candidates') and implies the output uses report-date prices, but it does not materially extend the schema's parameter documentation.

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 verb ('Get') and resource ('portfolio summary header for an institutional 13F filer'), then enumerates the exact contents: tracked 13F value, position count, concentration, turnover, and report dates. This clearly distinguishes it from sibling tools like GetInstitutionPortfolio or GetInstitutionQuarterlyActivity.

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 gives a concrete usage directive: resolve exact CIKs with SearchInstitutions, and warns that ambiguous partial names return candidates rather than auto-selecting. It does not explicitly contrast with sibling tools or state when not to use it, but the focused resource definition makes the intended use clear.

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