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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false. The description adds that results are shown as cards in the given order with View profile links to a specific domain and that only public Wellspent data is shown—useful context beyond annotations. It does not describe error behavior for invalid slugs, but that is minor for a read-only tool.

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?

Four sentences, front-loaded with the prerequisite, followed by the function, link behavior, and exclusions. Every sentence provides actionable guidance with no wasted text.

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 format need not be explained. The description covers prerequisite, input source, limit, order, link destination, and data scope, which is complete for a simple read-only card-display tool.

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% and the slugs parameter is documented in the schema. The description adds that slugs come from search_fee_only_advisors results and that order matters, which is not stated in the schema, so it provides value beyond structured fields.

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 ('show') and resource ('advisor cards'), including limit (up to 8), ordering, and link behavior. It names the prerequisite sibling search_fee_only_advisors and explicitly excludes advisors not from a Wellspent search, making it distinguishable from siblings.

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?

Explicitly says to use after search_fee_only_advisors and to pass slugs from its results. It also explicitly says not to use for advisors that did not come from a Wellspent search, covering both when to use and when not to use.

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