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

No annotations are provided, so the description bears the full burden. It signals an informational tool ('How to contact...') and refers to a quote link, which implies a read-only retrieval, but it does not explicitly state what is returned, whether it only returns a link, or whether any external navigation occurs. The transparency is adequate for such a simple tool but not detailed.

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 a single sentence that front-loads the core purpose and contains no filler. It earns its place by communicating the connection to contact and quote-link retrieval, though the 'or request' wording adds slight ambiguity.

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 no-parameter, no-output-schema tool, the description is minimally sufficient but incomplete where it matters: it does not say what the response contains, and it fails to disambiguate from the sibling request_quote tool. An agent could reasonably select the wrong tool when a user asks to actually request a quote.

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 input schema has zero parameters, so the baseline is 4. There is no parameter meaning for the description to add, and the description appropriately focuses on the tool's informational output.

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 title 'Get contact / quote link' and the description make clear this tool provides contact information and a link to request a quote for BuiltToWinWeb. The description is less crisp, using 'or request a free project quote,' which could be read as a write action rather than retrieving a link. It is distinguishable from siblings by its contact/quote-link focus, but it does not explicitly contrast with request_quote.

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?

There is no guidance about when to use get_contact instead of request_quote, get_pricing, get_services, or list_offerings. The phrase 'or request a free project quote' even suggests overlap with request_quote, leaving an agent to guess which tool actually generates a quote request versus merely provides a link.

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