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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds meaningful context beyond that: it is a static rules/field-definition payload rather than live account data, and it hints at the domain constraint 'no hard credit pull to apply.' It does not describe payload structure, but with no output schema and a trivial read, this is close to complete.

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 covering product, audience, and return contents, followed by a short imperative. It is front-loaded with the resource identity, though the 'Call this first' instruction sits at the end where it is slightly less prominent than it could be.

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, read-only retrieval with no output schema, the definition covers what it returns (agent rules plus the fields to collect from the owner) and when to call it (first). Nothing an agent needs to invoke it correctly is missing, though it could state whether the content is static or fetched live.

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. The description correctly implies no inputs are needed by framing the call as a straightforward 'call this first' retrieval, leaving nothing ambiguous about invocation.

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 names a specific resource (Clearwater Capital Group business funding application) and specifies the return content: 'the rules for agents and every field to ask the owner.' The verb is implicit ('Returns') but sufficient. It does not differentiate itself from the sibling create_review_link, which is why it falls short of 5.

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 closing imperative 'Call this first' gives explicit sequencing guidance, telling the agent to invoke this before proceeding with the application flow. It offers no when-not-to-use conditions or named alternatives, but the 'first' directive is the relevant usage signal for a zero-parameter bootstrap tool.

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