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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds useful behavior beyond that: pagination defaults (20), cap (50) and that a total is always returned, plus what each guide contains (curator, short intro). It does not mention auth or deep-link/UTM behavior, which is only visible in the schema.

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 front-loaded sentences: what it is, when to use it, then what to do next, closing with pagination facts. No filler or repetition, and the theme examples are compact and load-bearing.

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?

No output schema exists, so the description usefully discloses the return shape (id-bearing guides with curator and intro) and pagination totals. Only gap is the absence of guidance on `via` and on selecting between this and list_picks, both minor given full schema documentation.

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%, so via, city, limit and offset are already documented in detail. The description only restates pagination (default 20, max 50, total returned) and city coverage; it adds little on via or offset semantics, so baseline 3 applies.

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 resource (hand-made themed guides) with concrete examples of the themes and both covered cities, and explicitly separates itself from the detail tool: "Then call get_guide with an id." An agent can distinguish this from list_picks/search_shows without opening a schema.

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?

Gives clear trigger conditions ("Use when someone wants ideas, a theme, or 'what's special'") plus the explicit follow-up action ("Then call get_guide with an id"). It stops short of stating when NOT to use it or naming a sibling alternative such as list_picks, so it is strong but not complete on routing.

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