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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=false, so safety is covered. The description adds useful context: output includes ticket link (url), TripHook What's on page (whats_on), company links, and a see_more marker; it also states 'Public fields only, never a person', disclosing privacy filtering. It does not mention rate limits or pagination beyond see_more.

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, information-dense sentence followed by a directive. It front-loads the primary purpose and includes output hints efficiently, though it could be split for 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 two required parameters, no output schema, and read-only annotations, the description covers input formats, output fields, privacy, and a see_more marker. It misses explicit guidance on error handling (e.g., invalid city/date) and does not mention that city must be a lower-case slug beyond the pattern hint.

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 0%, so the description must compensate. It provides format hints: city slug and date YYYY-MM-DD, which map to the two parameters. However, it does not explain the city pattern (lowercase alphanumeric with hyphens) or max length beyond saying 'slug', leaving some schema-documented constraints unmentioned.

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 states a specific verb+resource: events happening in a city on a given date, plus traveler attendance. It explicitly distinguishes itself from siblings (which are about cities, destinations, and hooks) by naming TripHook links and the 'company' (other travellers) dimension.

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?

It says 'Use for any question about what is happening in a city on a date', which clearly scopes usage. However, it does not explicitly say when to use an alternative sibling (e.g., search_public_hooks) or when not to use this tool.

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