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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint:false, so the safety profile is covered; the description adds genuinely new behavioral semantics about how the result must be treated (advisory only, gated on enabled, subordinate to other signals). It does not discuss org-level authorization or whether entries can be stale.

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 dense sentences with no filler: the first defines the read and its output shape, the second defines the constraint on using that output. Both facts are front-loaded and each earns its place.

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 zero-param, read-only tool with an output schema and full annotation coverage, the description supplies the one thing structured data cannot: how to interpret and prioritize the returned taste. Only minor scoping details (per-org vs per-owner, whether entries can be empty) are absent.

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 the baseline is 4; nothing in the schema needs compensating for. The description still characterizes the returned values (enabled flag, entries ordered oldest first), which is a bonus rather than a parameter concern.

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 ('Read the org's learned taste') and names the two fields returned ('enabled' and saved entries, oldest first), so the agent knows exactly what it gets. It separates itself from remember_taste/forget_taste only implicitly through the read verb rather than by naming them.

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 conditional rule ('While enabled is false, do not apply the entries') and a precedence rule listing what outranks learned taste (request, brief, project, brand kit, exclusions, critics). It stops short of saying when to call it versus remember_taste/forget_taste, but the usage context is clear.

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