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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the "Read only" sentence is largely redundant. What the description does add is the content domain (the three channels and the confirmation email it documents), but it is silent on the shape of the return, since there is no output schema. Useful but thin beyond the annotations.

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, front-loaded with the purpose and ending with the sequencing rule, which is the most actionable part. The middle clause listing the three channels runs a little long but each element maps to real content. Minor redundancy with the "Read only" annotation.

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, read-only informational tool with no output schema, the description covers what it explains and when to consult it. It leaves the exact output format unspecified, but for a documentation-style tool that is a small 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 takes zero parameters, so there is nothing to disambiguate and the baseline is 4. The description correctly implies no input is required by framing the tool as purely explanatory.

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 states a specific purpose: enumerating the ways to reach a person at Portaur (message, callback request, email) plus the follow-up confirmation email. It names the downstream siblings send_message and request_callback, so an agent can tell it apart from the action tools. It is only loosely differentiated from the informational siblings about_portaur and ask_portaur, which keeps it from a 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?

Gives an explicit precondition: call it before send_message or request_callback to learn what to ask the person for. That is real routing guidance tied to named alternatives. It stops short of saying when not to bother calling it (e.g., if the needed details are already known).

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