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

Annotations already cover readOnly, idempotent, non-destructive, and closed-world, so the bar is lower. The description still adds the key operational fact an agent would otherwise worry about: it only produces a link and submits nothing. It omits whether the link expires or requires authentication, keeping 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 compact clauses with zero filler, and the non-submitting guarantee is front-loaded enough to be read before invocation. Minor awkwardness in opening with "The page where..." when the tool actually returns a link, not the page.

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 zero-required-parameter link generator with no output schema, the description covers what it produces (a link), what it does not do (submit), and the deal types in scope. Nothing an agent needs to call it correctly is missing.

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 67% — pha and topic carry descriptions, units does not. The description contributes the framing that all three are optional prefills, which clarifies intent, but adds no syntax or format detail for the undocumented units parameter.

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 concrete verb and resource — returns a link to a Janover Capital LLC financing-quote request page — and enumerates the eligible deal types (RAD conversion, Section 18 blend, PRAC, Component 2, refinance). The financing-quote focus is clearly distinct from the sibling tools get_rad_program_facts, size_rad_debt, and search_conversions.

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 audience and use case are explicit: a housing authority, developer or owner seeking a financing quote for a listed deal type. It does not name alternatives or state when-not to use it, but the domain is narrow enough that the intended trigger is unambiguous.

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