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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description adds entitlement ('Requires Pro'), the CURRENT-status filtering constraint, and the empty-cabinet no-result case. It stops short of describing the shape of the returned recommendation, which is the only meaningful gap.

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 with the core use case front-loaded, followed by failure conditions and sibling routing. No filler or repetition.

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 read-only recommendation tool with no output schema, the description covers when it works, when it returns nothing, and how it differs from siblings. Only the format/content of a successful recommendation is left implicit.

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 75% and the schema itself documents all four parameters thoroughly, especially the strict `context` analytics contract. The description only echoes prompt/weather as optional context and says nothing about `response_format` or the `context` requirement, so it adds little beyond the 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 and resource ('Picks from your owned cabinet') plus scope ('CURRENT status only') and inputs ('optional prompt/weather'). It explicitly distinguishes itself from the two nearest siblings by name, so an agent can route without opening either 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?

Names both alternatives and the condition that selects them: `ai_recommend` for discovery beyond the cabinet, `user_get_cabinet` for the full collection. It also states the two preconditions that cause failure — a Pro entitlement and a non-empty cabinet.

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