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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds 'refreshed weekly from venue and promoter calendars', providing context about data freshness and source. No contradiction with annotations, but no additional behavioral quirks are disclosed.

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?

Concise two-sentence description. The first sentence states the function and data source, the second gives usage context. Every word earns its place, with no redundant repetition of schema or annotation details.

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?

The tool has no output schema, so the description should help the agent understand what to expect. It says 'Find upcoming events' but doesn't explain return structure or result count. The 'refreshed weekly' clue implies potential staleness but lacks specifics. Overall, adequate for a simple search tool but missing some practical details.

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 covers 67% of parameters with descriptions (query and days_ahead). The island parameter lacks a description, relying on enum values. The tool description does not compensate for this gap. Since coverage is moderate, and enums are self-explanatory, the baseline applies, and the description adds minimal parameter meaning beyond the schema.

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 uses a specific verb 'Find' with a clear resource: 'upcoming events, concerts, festivals, and nightlife across the Hawaiian islands.' This distinguishes it from sibling tools like find_hawaii_restaurants or search_hawaii_tours, which target different domains.

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?

Explicitly states when to use: 'Use when users ask what's happening in Hawaii or want entertainment options.' This gives clear context, though it doesn't explicitly name alternatives or exclusions. It still provides sufficient guidance for an agent to select this tool over siblings.

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