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

With no annotations, the description carries the full burden and does so exceptionally well. It discloses grading thresholds (strong_buy >= +80, buy >= +70, neutral between -70 and +70, sell <= -70), clarifies that there is no strong_sell tier, explains the informational-only nature, and details the payment mechanism and required header. This gives agents full visibility into the tool's behavior and constraints.

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?

Although long, the description is exceptionally efficient: it starts with the core action, then provides the grading logic, pricing, and a comparison with the sibling tool. Every clause adds necessary information, and the structure is logical and easy to parse. It avoids fluff and tautology.

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?

The description is comprehensive for a paid, standalone tool. It covers output format (verdict, score, price, per-timeframe breakdown), grading interpretation, payment cost, authentication (402 challenge), alternatives (`pitch`), and limitations (informational only). No critical information is missing for correct invocation and interpretation.

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 `symbol` as 'Area, e.g. downtown, marina, Palm Jumeirah', and the description enriches this by stating it accepts 'area id or English name' and lists example areas (42 areas: downtown, marina, palm, jvc, businessbay, dubaihills …). This goes beyond the schema, giving agents concrete, actionable parameter guidance.

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: 'Return the bottom/top verdict for one Dubai area property market' and specifies the resource (property markets) and the 42-area universe. It also distinguishes itself from the sibling tool `pitch` by noting it answers any symbol in the covered universe, providing clear differentiation.

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 explicitly contrasts this tool with `pitch`: 'The free `pitch` tool shows a live verdict for this market's showcase symbol only — this tool answers ANY symbol in the covered universe and returns the per-timeframe breakdown.' It also provides payment instructions and a retry strategy for the 402 challenge, which are practical usage guidelines.

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