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

Goes well beyond the annotations by disclosing the entitlement model: without a paid plan a list returns its first 5 rows plus locked.count and locked.by_type, records name a subject plus 3 related names per section, and contact values/decision-maker names are withheld as types and counts only. It also explains that every answer reports what it withheld via `entitlement` and `locked`.

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 core content is front-loaded and the access paragraph earns its place by explaining withheld data, but the opening is a single overloaded run-on that embeds the entire return-field list, and the closing sales line with the plans URL is promotional filler.

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 does the work of listing the returned fields and the entitlement/locked mechanics, which is what an agent needs for a read-only search. The remaining gap is pagination and `limit` semantics, but the tool is otherwise complete enough to call correctly.

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 43%, so the schema alone does not carry the parameters. The description maps the window semantics to `from`/`months` (default 24 months from today) and names the sponsor, lien and minimum-principal filters, but says nothing about `limit` or `cursor`, leaving pagination behavior undocumented.

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 and resource ('debt facilities still on a BDC schedule whose ... maturity falls inside the window'), the default scope (next 24 months from today), and the ordered return fields. It is clear on its own, but it never differentiates itself from the close sibling 'debt_maturity_schedule', leaving the agent to infer the boundary.

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 window defaults, the filter axes (sponsor, lien, minimum principal), and the note that 'a BDC that tags no maturity contributes nothing here' sketch the context. There is no explicit when-to-use statement and no named alternative to distinguish it from 'debt_maturity_schedule'.

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