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

readOnlyHint=true already tells the agent this is a read operation, so the description doesn't have to establish that. It adds value beyond the annotation by stating what the tool returns (a pointer URL) and by explicitly rejecting capabilities it does not have, which stops the agent from assuming it can transact. The description doesn't mention formats, expiry, or opening behaviour, so it isn't a full behavioural account.

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?

Two sentences, and the most important constraint (this is a pointer only) comes second, right after the agent learns what it returns. Every clause carries information, so there is no waste.

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?

This is a simple tool with no parameters, one annotation, and no output schema. The description covers what it returns (a URL), what it does not do (book or transact), and the user's intent that selects it, which is everything an agent needs to call it correctly.

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 no parameters and takes no input, so the description has no input semantics to document; the baseline for a no-parameter tool applies. Nothing in the description contradicts the empty schema.

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?

A specific verb plus a specific resource: it returns the URL where a human can start a conversation or book a consultation. The negative framing ('pointer only') makes clear this tool exposes a link and nothing more, which lets an agent tell it apart from siblings like get_faq or get_offering that return content rather than a contact path.

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 description conveys when to use it (the user wants to talk to a human or book a consultation) and what it cannot do (book, schedule, quote, or transact), which prevents the agent from expecting the server to take an action. It stops short of naming a specific alternative, so the guidance is strong but not exhaustive.

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