sixflags_suggest_next

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so safety is covered; the description adds real behavioral detail beyond that: only currently-operating rides are considered, ranking is by standby wait, and the park defaults to the home park (Carowinds). It does not disclose return shape or how stale the underlying wait data may be, which for a live-crowd recommendation tool would be useful.

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?

Three sentences, front-loaded with the core action and its ranking rule before the usage tip and the default park. The middle sentence is mildly promotional but earns its place by conveying repeat-call semantics; there is no padding.

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 read-only recommendation tool with no output schema, the description covers the action, ranking basis, filters, repeat-usage pattern, and the default park. The main gap is the shape of the response (e.g. ordered list of rides with waits), which an agent might want since no output schema is provided.

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 all four parameters are already documented in the schema, and the description largely restates them ('exclude rides you've already done and cap the wait' mirrors the schema's exclude and maxWaitMinutes descriptions). It adds no format or syntax detail beyond the schema, making the baseline 3 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?

States a specific verb and resource ('Recommend which attraction to ride next') and immediately specifies the ranking criterion ('ranks currently-operating rides by shortest standby wait'). This clearly separates it from data-fetching siblings like sixflags_get_wait_times or sixflags_list_attractions, which return raw data rather than a ranked recommendation.

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?

'Use this repeatedly through the day to keep hopping to the lowest-wait ride' gives clear situational context for when to invoke it. It does not, however, name the alternative raw-data tools (get_wait_times, list_attractions) or state when NOT to use this tool, so it stops short of explicit routing.

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