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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds genuinely new behavior: results are ordered cheapest-first and guaranteed non-empty ('never a dead end'), with a floor of free nonprofit credit counseling. It does not disclose the shape of each returned option, which would have completed the picture.

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 sentence with the core mechanic front-loaded and the ordering constraint stated before the fallback floor. The 'rungs'/'decline-with-dignity' phrasing is colorful but costs little and no sentence is wasted.

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?

No output schema exists, yet the description never says what a returned option looks like (program name, why it fits, cost), so the agent cannot anticipate the response. For a 7-parameter recommendation tool this is adequate on intent but incomplete on payload.

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 29% (state and industry are documented, the five enum parameters are not), so the description carries most of the burden. It offers only 'optional profile bands' as a hint that the extra parameters are optional narrowing filters, with no explanation of how any band affects the waterfall.

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?

Names a specific transformation: given a decline reason, return the next options to try, ordered cheapest-for-the-owner first and ending at free nonprofit credit counseling. An agent can distinguish this from find_lenders or estimate_match because it is explicitly a post-decline recommendation waterfall, not a lender lookup or match score.

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 'given why a business was declined' framing implies the trigger condition (use after a decline) but never states when to use this versus find_lenders or estimate_match, nor any exclusions. Usage is inferred rather than directed.

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