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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds valuable behavioral detail beyond annotations: the dual-mode return behavior (titles vs venues with editorial notes) and the fact that lists are hand-curated. This enriches the agent's understanding of what to expect from the call.

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 two sentences, front-loaded with the core purpose and example, then succinctly explaining behavior for both invocation modes. No filler or redundancy; every clause contributes useful information.

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?

With only two parameters (one required), an output schema, and annotations indicating a safe read operation, the description covers both call variants and notes the presence of editorial notes. It does not need to describe return fields because the output schema exists. The information is complete for an agent to select and invoke the tool effectively.

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 describes city as 'City name or key' and list_id as 'A list id from the no-arg call'. The description reinforces and expands this by explaining that list_id changes the output from list titles to venues with editorial notes, and that list_id comes from the no-arg call. This adds meaningful semantic context beyond the schema, even though schema coverage is 100%.

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 clearly states the tool's function: listing Dim Hour's hand-curated themed lists for a city. It distinguishes from siblings like list_cities and list_new_venues by specifying 'hand-curated themed lists' and provides a concrete example ('Unmarked Doors' speakeasies). It also explains the two modes (with and without list_id), making the purpose fully unambiguous.

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?

The description provides clear context on how to use the tool: call without list_id to get all list titles, and with list_id to get venues with editorial notes. It implies using this tool when curated lists are needed, but does not explicitly mention when to avoid it or name alternative sibling tools for other list types. Thus it gives clear usage context but lacks explicit exclusions or alternatives.

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