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

readOnlyHint=true already tells the agent this is a safe read. The description contributes real value by enumerating the response facets (registration, inbox, transport status), but it omits what happens on an unknown address (error vs. empty result) and any auth or rate-limit constraints on the lookup.

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 front-loaded sentence with the action, the input example, and the output contents. No filler or repetition.

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 one-parameter read tool with no output schema, the description covers the essential concerns: what to pass in and what categories of data come back. The only meaningful gap is not-found/error behavior, which is minor given the tool's simplicity and the readOnly annotation.

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 schema has 0% description coverage, so the description must carry the single parameter. It does partially: "@name" gives the expected address form, which the bare string type does not. However, format rules for the address (domain-like vs. handle, casing, validation) remain unspecified.

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 gives a concrete verb ("look up") and resource ("an agent address such as @name") and even states the returned data (registration, inbox, transport status). It is specific enough to act on, but it does not distinguish itself from plausible siblings such as ventru_find or ventru_search_providers, so an agent must infer which lookup tool is appropriate.

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?

Usage is only implied: the reader infers this is the tool for resolving a known @address rather than searching. There is no explicit when-to-use, no when-not-to-use, and no named alternative among the many siblings (find, search_providers, trust_profile).

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