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

No annotations are provided. The description mentions payment details and the need for a PAYMENT-SIGNATURE header on retry, but does not explicitly state whether the tool is read-only, destructive, or any side effects. With no annotations, the description carries the burden but only partially addresses behavioral traits.

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 well-structured with the core purpose first, followed by payment details and usage guidance. It is slightly verbose with the payment and trial info but remains focused. Each sentence adds value.

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 one parameter and no output schema, the description covers the output (ranked list), comparison with 'pitch', and cost model. It lacks details on the return format (e.g., area names vs. scores) but is largely complete for a simple 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?

The only parameter 'limit' is fully described in the schema (default 5, max 42) with 100% coverage. The description does not add additional semantic meaning beyond the schema, meeting the baseline for high 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 starts with 'Scan all 42 Dubai areas and return those closest to a top (overheated), ranked most-top first.' This clearly specifies the verb (scan), resource (42 Dubai areas), and output (ranked list of top areas). It also distinguishes from siblings by noting that 'pitch' tells how many, while this names them.

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 contrasts with 'pitch' (free, tells count) and implies use when you need the actual names. It also states 'BEST COLD START: you do not need to pick a symbol' suggesting ideal initial use. However, it does not explicitly state when not to use or list alternatives.

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