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

Annotations already cover the read-only, non-destructive nature of the tool. The description adds useful behavior context by listing the returned fields and noting the special long-form story condition for Iconic 50 venues. However, it does not disclose behaviors such as parameter precedence, required city context, error cases, or rate limits.

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 front-loaded sentence that states the primary purpose immediately and then uses a compact field list to convey the response contents. Every phrase earns its place with no redundant filler.

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?

Between the explicit field list, the Iconic 50 conditional, the read-only annotations, and a fully described input schema, an agent can understand what this tool returns and that it is a safe read operation. The main gap is the lack of guidance on how to choose among id, city, and name when invoking the tool.

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 the schema already documents id, city, and name. The description adds no additional parameter-level meaning, such as how id and name interact or why city is required, so it stays at the baseline for high schema coverage.

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 identifies the action ('Get') and the resource ('the full Dim Hour record for one venue'), then enumerates the exact content fields returned. This distinguishes it from the list/search siblings, which operate over multiple venues, by emphasizing a single-venue detail lookup.

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 gives no explicit guidance on when to use this tool versus alternatives like search_venues or search. It implies a detail-lookup purpose ('full record for one venue'), but does not tell the agent to first obtain a venue id via search_venues or explain the role of the required city parameter.

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