searchFundDisclosures

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

Annotations already provide readOnlyHint, idempotentHint, openWorldHint. Description adds context on return fields (CIK, entity info, file number) but no additional behavioral traits like rate limits or authentication. Value added beyond annotations is moderate.

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?

Two sentences- front-loaded with primary purpose, second sentence adds useful return details. No extraneous text.

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 search tool with one parameter and annotations covering safety, the description explains what is returned and references the API. It lacks pagination or limit info but is sufficient for a basic search. Slightly better than adequate.

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% and describes 'name' as 'Name of the holder to search for'. Description reinforces 'by name' but does not add new semantic constraints or examples. Baseline 3 is appropriate.

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?

Description clearly states 'search for mutual fund and ETF disclosures by name', with specific verb and resource. It distinguishes from sibling tools like getFundDisclosure by indicating it returns multiple disclosures based on name search, and lists expected details (CIK, entity info, file number).

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?

Description implies usage when searching by fund name but does not provide explicit when-to-use or when-not-to-use guidance, nor names alternatives among the many sibling tools. Usage is implied but not differentiated.

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