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

The readOnly/idempotent/non-destructive annotations already establish the safe-read profile, so the description only needs to add context beyond that. It contributes the notion that records are 'observed providing capital' and that fund size and average investment are 'kept apart', which hints at inferred/confidence-scored data, but it says nothing about result limits, ranking, or what confidence means despite a 'confidence' sort option.

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?

A single dense paragraph, front-loading source scope and record fields before the filter list. Nearly every clause carries information; the only mild waste is pairing 'mezzanine and private equity funds' without distinguishing them.

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 usefully enumerates the returned fields (provider type, strategy, fund style, fund size, average investment, vintage, SBIC licence, new-investment status, mandate summary), which is exactly what an agent needs for a read tool. The remaining gap is the semantics of sort/limit/query on a 9-parameter 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 description coverage is only 33%, so the description must compensate. It does map several filters to meaning (state, provider type, sector-as-free-text, SBIC status, fund size), but leaves sort, limit, query, and making_new_investments entirely unaddressed, and adds nothing to the provider_type enum beyond what the schema already states.

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 the resource precisely (SBICs, mezzanine/PE funds, family offices that fund independent sponsors) and enumerates the attributes carried on each record, so an agent knows this is a filtered provider search rather than a deal or firm lookup. It stops short of explicitly contrasting itself with close siblings like search_sponsor_deals or search_family_offices, so it earns a 4 rather than a 5.

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 only implied: the sentence 'Filter by state, type, sector text, SBIC status or fund size' tells the agent which filters exist, which indirectly signals when the tool is appropriate. There is no explicit when-to-use guidance, no statement of when another tool (e.g. find_capital_for_opportunity) is preferable, and no prerequisites.

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