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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that: it discloses the privacy boundary (no phone, street address or coordinates) and an edge-case behavior (instant quote persists when no purchasable catalogue exists).

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?

Three short sentences, front-loaded with the core verb+resource and key. The privacy and catalogue sentences earn their place, though the "instant quote" clause is somewhat cryptic without more context.

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?

An output schema exists, so return-shape explanation is rightly omitted. The description covers keying, visibility limits, and the no-catalogue edge case; the only gap is the absence of explicit routing guidance to or from sibling lookup 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?

Schema description coverage is 100% for the single publicReference parameter, so the schema already documents the slug and its origin in search_traders. The description's "by listing slug" adds no format or validation detail beyond that; baseline 3 applies.

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?

States a specific verb and resource ("Return a public directory profile") and the key used to fetch it ("by listing slug"), which implicitly separates it from search_traders and browse_trades. It stops short of naming a sibling explicitly, so the differentiation relies partly on the schema's reference to search_traders.

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: you need a listing slug, which the schema says comes from search_traders. There is no explicit when-to-use/when-not, no stated prerequisites, and no named alternative for fetching trader data by other keys.

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