find_similar_managers

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

No annotations are provided, so description carries full burden. It clearly explains that returns are disclosed institutional positions, not manager intent, and that direction ('similar' or 'unlike') controls behavior. Lacks details on edge cases or performance, but is adequate for 4 params.

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?

Description is concise with clear sections: research warning, purpose, args in bullet-like format, and returns. No unnecessary words, front-loaded with important caveat.

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?

Given 4 params, no output schema, and no annotations, the description adequately covers inputs and output structure. Returns object described with fields and disclaimer. A minor gap: no mention of error handling or data source limitations beyond the explicit warning.

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 has 0% description coverage, but description explains each parameter: holdings with example format (ticker and weight), quarter defaults to latest, top_n range, direction enum with meanings. Adds value by clarifying weight optional and defaults.

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 states the tool matches a portfolio against the 13F universe and returns closest or deliberately-different managers, specifying verb (match) and resource (13F universe). It also distinguishes from siblings like get_manager_holdings by focusing on similarity search, not individual holdings.

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 description explicitly states 'Research data only' and warns about inferring manager intent, indicating when to use. However, it does not explicitly contrast with alternatives like search_managers or get_consensus_portfolio, though the unique purpose is clear.

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