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

Annotations already declare readOnlyHint=true, idempotentHint=true, and non-destructive, so safety is covered. The description adds genuine behavior beyond that: what the response contains (rules, palette, save timestamps, reference names) and the 'status empty' branch with its prescribed next action. It stops short of pagination or error/auth behavior, but the empty-state disclosure is real added value.

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 action, then usage, then the empty-state branch. Every sentence carries distinct information with no repetition of structured fields, aside from restating the title.

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-value documentation is not strictly required, yet the description still names the salient fields and timestamps. Combined with the empty-state routing, the precondition for calling, and the (schema-side) irrecoverable-key warning, an agent has everything needed to invoke this correctly.

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 coverage is 100%, with the single parameter already documented including its tp_ pattern and the warning that it is not recoverable. The description only references profile_key in passing ('for a user who has a profile_key') and adds no syntax or format meaning beyond the schema, so the 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 (read) and resource (taste profile), and immediately clarifies what it returns: saved style rules and palette. It is clearly distinguished from siblings like save_profile, delete_profile, and describe_style, which is named as the fallback when nothing is saved.

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 trigger ('before creating slides, an interface, an image or any design for a user who has a profile_key') and an explicit alternative for the empty case ('use describe_style and ask the user to confirm rules'). Both when-to-use and when-not-to-use are covered with a named sibling.

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