sixflags_list_attractions

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

Annotations already declare readOnlyHint=true, so the description correctly reinforces that it returns static, not live data. It adds context about including map coordinates and that it is a full directory, but does not go beyond the read-only nature already indicated by 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-loaded with the core purpose, and every sentence adds value. No superfluous words.

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 tool's simplicity, the description fully covers its purpose, parameters, default behavior, and relationship to sibling tools. No output schema is needed, as the description implies the expected items (attractions with map coordinates).

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 both parameters are already described. The description adds the default value for 'park' (home park Carowinds), providing extra context beyond the schema, but does not elaborate on the enum values or format.

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?

Clearly states that it lists attractions, shows, or restaurants at a Six Flags park, including map coordinates. Distinguishes from siblings by specifying it provides static metadata and not live wait times, with an explicit reference to sixflags_get_wait_times for current status.

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?

Provides explicit usage guidance: use sixflags_get_wait_times for current wait times, defaults to home park (Carowinds), and clarifies that it lists static metadata. Also implies the type parameter can be set to different entity kinds.

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