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

It discloses a two-phase matching strategy (strict all-words then broad any-word), verified alias handling, ordering by largest positions in the recent bucket, and valuation fallback behavior. It also explains that unmatched words are never discarded by downstream scoped tools. This goes well beyond the readOnly/destructive annotations and has no contradiction.

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 purposeful, front-loading the core searchable set and layering matching, ordering, and result contents. The final sentence about downstream scoped tools is tangential for invoking this tool but adds useful context. No filler or redundancy otherwise.

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?

With no output schema, the description supplies essential return semantics: included fields (latest report date, tracked value, position count), ordering, and valuation caveats. It does not spell out the exact response envelope or behavior for zero/no-match cases, but an agent has enough to invoke and interpret results correctly. Given two simple parameters, this is adequately complete.

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 input schema already documents the query and maxResults parameters with 100% coverage, so the baseline is met. The description adds query interpretation details (punctuation-independent word matching, strict-then-broad semantics, alias expansion) that let an agent form a good query. It does not add anything specifically about maxResults beyond the schema description.

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 ('tracked 13F filer set') and the two query keys (institution name or SEC CIK), so an agent can identify what is searched. It is distinct from generic search siblings like SearchInvestmentAdvisers or SearchFunds. This is more than a restatement of the title.

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 establishes a clear use context: resolve and compare 13F filers by name or CIK before calling a scoped institution tool. It does not explicitly name alternative search tools or state when not to use this one, so it falls short of full routing guidance.

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