What should I wear tonight?

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

Annotations already declare read-only, idempotent, and non-destructive behavior, so the safety profile is covered. The description adds value by revealing that recommendations are scored with community compliment, office-safety, and versatility data, but it does not explain potential output variations or edge behavior.

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?

A single, front-loaded sentence expresses the tool's purpose, decision inputs, and scoring context. It includes helpful examples without lengthy padding, making it easy for an agent to scan.

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?

The description explains the reason for being and the key decision variables, and it notes the data source behind scoring. However, with no output schema, it does not clarify whether the response is a single fragrance, a ranked list, or requires additional follow-up, which would help an agent set expectations.

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 100%, so parameters are already documented at the schema level. The tool description reinforces the spirit of occasion and season with examples, but it does not add any required meaning beyond what the schema already states.

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 clearly presents the tool as a time-sensitive fragrance suggestion driven by mood, occasion, and season. It distinguishes itself from search/get/similar siblings by emphasizing 'for right now', but it does not use an explicit verb like 'recommends' and does not name the most similar sibling, get_recommendations.

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?

The occasion examples ('date', 'office tomorrow', 'night out', 'cozy evening in') and the 'right now' framing signal when this tool should be used. It does not explicitly state when not to use it or draw a contrast with get_recommendations, but the intended context is clear enough for an agent to spend some time.

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