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

Annotations already declare this is a safe, read-only, idempotent operation. The description adds useful context beyond annotations: the request is routed to Janover Capital LLC, the service is free and non-obligatory, and Janover arranges loans rather than selling fund interests.

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 wasted words. The core purpose is front-loaded, followed by routing and scope clarification, both of which earn their place.

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-parameter link tool with no output schema, the description covers who it is for, what it provides, where it routes, and the commercial nature of the service. It does not explicitly say whether the link is returned as a URL or opened directly, which is a minor remaining gap.

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 has zero parameters, so the baseline is 4. No parameter semantics are needed, and the description does not need to compensate for schema gaps.

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 identifies a specific resource—an Opportunity Zone debt-financing request link—and distinguishes it from the calculation and lookup siblings. It is clear enough to select the tool, though the phrasing 'Link where...' describes the destination more than stating the tool's action (e.g., 'Returns a link').

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?

It names the intended audience (developer, sponsor, business owner) and the project context (Opportunity Zone), and notes the service is free with no obligation. However, it does not explicitly say when to use this versus alternatives or when not to use it, leaving usage guidance implied.

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