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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds meaningful context beyond that: 'Returns a link only; it submits nothing,' which preempts the natural assumption that a 'request a quote' page might initiate a submission. It does not say whether the link is static or expires, which is a minor gap.

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 sentence with no filler, and the key constraint ('returns a link only') is placed at the end where it lands clearly. It opens with a noun phrase rather than a verb, which is slightly less scannable than a direct action statement, and the parenthetical list of deal types makes the sentence long.

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 input schema to explain and no output schema, the description carries the return-value burden itself and does so by stating it returns a link. The domain context (who the lender is, what deal types the desk handles) is sufficient for an agent to route a user here. Only the link's nature (static vs. expiring, single-use) is left unstated.

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?

The tool takes zero parameters, so the baseline is 4. There is nothing for the description to disambiguate, and the schema's additionalProperties=false confirms no input is expected.

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 states precisely what the tool returns: a link to the page where a developer or owner requests a LIHTC financing quote from Janover Capital LLC, enumerating deal types (4%/9%, construction, bond, bridge, permanent, Year 15). It is clearly distinct from the sibling calculators and property lookups, though it never names a sibling explicitly.

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 intended caller and situation are implied (a developer or owner seeking a financing quote), and the closing clause rules out expecting a submission. However, there is no explicit 'use this when...' statement and no comparison to alternatives such as get_equity_pricing or get_applicable_percentages, leaving the agent to infer when this link is the right destination.

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