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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description is free to add genuinely new behavior: a 10-item unlock threshold and the fact that below it the call returns a remaining-count instead of the portrait. That gating behavior is the single most useful thing an agent could know here and would be invisible otherwise.

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 sentences, front-loaded with the return contents, then the usage trigger, then the gating caveat. No restatement of the title and no filler; every sentence changes how an agent would call the tool.

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?

With no parameters, no output schema, and safety already covered by annotations, the description supplies exactly the missing pieces: what comes back and what happens before the 10-item threshold. An agent has everything needed to decide whether to call it and to interpret a below-threshold response.

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 no parameter semantics to explain and the baseline is 4. Nothing in the description misleads about inputs, and the schema is trivially complete.

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 names a specific verb and resource ('Get the user's full Taste Portrait') and then enumerates the exact contents (archetype, essence, core tension, preoccupations, unowned recommendation, blind spot). It also explicitly distinguishes itself from the compact portrait already in context, so an agent can tell when this deeper call is the right one.

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?

'Call this to go deeper when they ask about their portrait' gives a concrete trigger, and the compact-in-context note implies the alternative for shallow needs. It stops short of naming a sibling tool or stating an explicit when-not condition, so the routing is clear but not fully spelled out.

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