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

Annotations already establish that this is a safe, read-only, idempotent lookup. The description adds useful content scope by naming the fairs, dates, venues, sites, and hotel costs it returns, but it does not state data freshness, coverage limits, or whether prices are live.

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?

It is a single well-formed sentence with no redundant phrasing. The subject is front-loaded and every phrase contributes to describing the returned 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?

For a zero-parameter, read-only lookup with no output schema, the description gives a useful summary of returned fields. It could be more complete by stating whether hotel prices are live, which fairs are covered, or what time period is represented.

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 tool takes no parameters, so there is no parameter meaning that the description must explain. The baseline for zero-parameter tools is 4, and the description does not confuse the absence of inputs.

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 subject and content: Art Basel Miami Beach and surrounding fairs, including dates, venues, sites, and nightly hotel costs. It is understandable without the title, but it does not explicitly distinguish itself from siblings such as hotel_prices or event_details.

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?

There is no guidance on when to use this tool versus alternatives. Given siblings like hotel_prices, event_details, and whats_on, an agent would need outside knowledge to know whether this is the right tool for a pricing or event question.

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