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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's main added value is the Pro-account entitlement gate, which is a real behavioral constraint an agent must check before calling. It omits anything about paging behavior for a list endpoint that has limit/cursor.

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 tight sentences, purpose front-loaded, precondition immediately after, and cross-references last. No filler.

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 simple read-only list tool whose annotations already declare the safety profile and which has no output schema, purpose, entitlement, and sibling routing are all covered. Only pagination semantics are missing, which is a minor but noticeable gap given `cursor`/`limit` exist.

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 only 25% (only `context` is documented), so the description carries the burden of explaining `limit`, `cursor`, and `response_format` — and it says nothing about any of them, not even that results are paginated. The self-documenting defaults/enum mitigate this slightly, but the gap is real.

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?

Specific verb plus resource plus scope: 'Get your fragrance wishlist.' The see-also line explicitly separates it from `user_get_cabinet` (owned fragrances) and routes item-level lookups to `fragrance_get`, so an agent can distinguish it from the closest sibling without opening a schema.

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 a hard precondition ('Requires a Pro account') and names two complementary tools with the condition that selects them (details vs. owned items). It does not explicitly say when not to use it versus e.g. `user_get_collections`, so it stops short of full when/when-not guidance.

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