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

Annotations declare destructiveHint=true and readOnlyHint=true simultaneously, which is contradictory. The description says nothing about behavior beyond the output being 'curated formulas.' It doesn't explain what destructive means here (likely none) or how the tool behaves. This is a serious gap because the annotations are ambiguous.

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 sentences, tightly focused. The list of occasions is a useful summary of allowed values, and nothing is wasted.

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 tool has 6 parameters with full schema descriptions and no output schema. The description covers the core purpose but fails to explain what the output looks like (e.g., a formula, a list of items) or how weather parameters interact with the result. It's adequate but leaves gaps.

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%, so parameters are fully documented in the schema, including weather-related nuances. The description adds an occasion enumeration but doesn't add syntax or format details beyond what's in the schema.

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 states a specific verb ('Get') and resource ('curated outfit formulas') with the key dimensions (occasion, weather). It's clear what the tool does, but it doesn't differentiate from siblings like what_to_wear_today, which likely has overlapping purpose.

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?

No guidance is provided on when to use this tool versus siblings such as what_to_wear_today or about_outfitmaker. The description lists occasions but doesn't say when this is the right choice.

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