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

Annotations already declare readOnlyHint, idempotentHint, etc. The description adds real-time context ('today's real golden hour / blue hour times', 'current light quality score') and specific outputs (camera settings). No contradictions with annotations.

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 front-load key outputs and use case. No filler words; every phrase adds value.

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?

Given the output schema (present but not shown) and annotations, the description is sufficiently complete. It explains what the tool returns and when to use it, though it could mention pagination or format if relevant.

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?

The schema has 100% coverage with one optional enum parameter. The description adds that omitting the location returns all 6 locations, providing a slight enhancement over the schema. Baseline 3 is appropriate.

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 states the tool returns Sedona photography locations with golden hour/blue hour times, light quality score, and camera settings. It uses specific verbs and resources, distinguishing it from sibling tools like get_stargazing_conditions or get_sun_times.

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 description says 'Great for landscape and astrophotography planning,' which implies appropriate use cases. However, it does not explicitly state when not to use or provide alternatives among the many sibling tools, so it's not fully explicit.

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