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

Annotations already cover safety (readOnly, non-destructive, closed-world). The description adds meaningful behavioral context beyond that: the data source (NWS latest observation and alerts) and the crucial temporal caveat that this is current conditions, not a forecast. It doesn't mention freshness windows or rate limits, but the additions are substantive.

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-loaded with the usage trigger, followed by the data-provenance caveat. Every clause earns its place with no redundancy.

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 single-parameter read tool with no output schema, the description conveys the key content (weather, alerts, ride-down count) and the current-vs-forecast distinction. It could say a bit more about what 'rides are down' returns or freshness, but it is sufficient for correct invocation.

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% and the schema itself documents park_id thoroughly (canonical ID from parky_find_experience, park-key fallback). The description adds nothing about the parameter, so the schema does the heavy lifting and baseline 3 applies.

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 (retrieve current park weather and ride-down counts) and scopes it to 'one supported park right now'. This clearly distinguishes it from siblings like parky_get_waits, parky_get_hours, or parky_get_ride_outages.

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 explicit trigger conditions ('when a visitor asks about weather, storms, heat, lightning, weather alerts, or how many rides are down'), which is strong contextual guidance. It does not, however, name an alternative tool or state when NOT to use it, so it stops short of the 5-level routing clarity.

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