FundBiz Lender Index

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

With no annotations, the description must carry the behavior burden, and it does state 'Read-only' plus the provenance distinction (editorial research, not a lender panel), which matters for interpreting the rating. It leaves out result-count limits and pagination behavior, which keeps it short of a 5.

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?

Three tight sentences with no waste; the scope and provenance caveat are front-loaded before the filter and return details.

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 read-only, 5-optional-parameter search tool with no output schema, the description enumerates the returned factual fields and rating, and flags the read-only nature, so an agent has enough to call it correctly. Only result-size/pagination behavior is unaddressed.

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 100%, so all five filter parameters are already documented in the schema; the description only restates the filter categories without adding syntax or edge-case meaning. Baseline 3 applies since the schema does the heavy lifting.

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?

States a specific verb (search) and a precisely scoped resource (UK specialty business finance lenders reviewed by FundBiz), and explicitly disambiguates the data source as editorial research rather than a lender panel. The filter axes and returned fields are named, so the agent knows exactly what this tool is.

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?

Names the three filtering modes (free-text query, product type, eligibility flags) so the agent knows the available entry points, and the editorial-research framing tells it what kind of results to expect. There is no explicit when-not guidance, but with no sibling tools there is no competing alternative to route away from.

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