sixflags_get_wait_times

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

Annotations already declare readOnlyHint=true, so the agent knows it's safe. The description adds richer behavioral details: returns every attraction with status (operating/closed/down), standby and single-rider waits, sorted longest-wait first, and a park crowd-level summary. No contradiction.

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?

The description is a single sentence that packs all key information (purpose, default, output format, sorting, crowd summary) without unnecessary words. It's front-loaded and efficient, though splitting into two sentences could improve readability.

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 no output schema, the description fully explains the return structure (attractions, status, waits, sorted, crowd level). Both optional parameters are covered. No output schema makes this level of detail appropriate and sufficient.

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% with both parameters described. The description adds context beyond the schema: it clarifies the default park (Carowinds) and the default for openOnly (false means include closed/down). This helps the agent understand defaults without calling the tool.

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 verb (Get), resource (ride wait times), and scope (Six Flags park, defaults to Carowinds). It distinguishes from siblings like sixflags_list_parks (lists parks) and sixflags_get_park_schedule (gets schedule), making its purpose unique.

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 explicit guidance on when to use this vs. alternatives. The context implies it's for retrieving real-time wait data, but it doesn't specify when to prefer it over sixflags_list_attractions or sixflags_suggest_next, nor does it mention when not to use it.

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