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

Beyond the annotations, the description adds useful behavioral context: PolicyVera sends nothing on the user's behalf, and the only side effect is counting how often the note is requested. This clarifies the non-read-only and non-idempotent hints without contradicting them, though it does not describe the exact return format.

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?

The description is only two sentences and does not waste words. It front-loads the purpose, although the colon-based phrasing in the first sentence is slightly awkward and leaves 'this' underspecified.

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 tool with no output schema, the description gives some useful context about what the note involves and what side effects occur. It remains incomplete because it does not clearly state the returned content or shape, and it offers no sibling comparison for an agent choosing among link and sharing tools.

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 there is no parameter semantics to explain. The baseline for a parameterless tool is 4, and the description does not create parameter confusion.

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 the resource as 'the words to pass on' and mentions PolicyVera's connect page and headline, so it is more than a title repeat. However, it never uses a clear verb like 'returns' or 'generates', and the referent of 'this' is ambiguous, leaving the agent to infer the exact purpose.

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 phrase 'someone the person wants to tell about this' implies the use case: sharing PolicyVera with a friend. It does not explicitly say when to choose this over siblings such as get_review_link, get_signin_link, or share_with_lender, nor does it give exclusions.

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