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

With no annotations, the description carries the behavioral-transparency burden. It does disclose that it is free, optional, and skippable, and that interest:false exits the process, which is helpful. However, it does not disclose side effects of the 'subscribe' phase (e.g., whether a charge occurs, a subscription record is created, or any persistent state changes), and it never mentions what is returned. This is a moderate gap for a funnel with an explicit paid subscription step.

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 compact and efficient: the first sentence immediately states it is optional and names the directly callable siblings, then the phase chain and bow-out condition follow in the remaining sentences. There is no redundant phrasing or wasted words, and the most decision-relevant info is front-loaded.

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 gives an agent what it needs to decide whether to invoke the tool and how to navigate the phases. But as there is no output schema and no annotations, a complete context would also mention what the tool returns (e.g., transcript/messages UI) and whether selecting 'subscribe' is safe or triggers a purchase. These gaps are not critical for selecting the tool but are relevant for invoking it in the real-estate agent context.

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 description adds substantial meaning beyond the sparse schema (33% coverage). It maps the phase parameter to its five enumerated stage values, assigns concrete meaning to interest ('bow out'), and critically constrains the sample parameter: any area other than downtown is answered by the paid evaluate_symbol instead. This level of parameter guidance meaningfully helps an agent chose arguments correctly.

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 tool as an optional intro/subscription funnel for the Dubai real-estate signal agent and defines a precise phase sequence ('hello' -> 'value' -> 'catalog' -> 'sample' -> 'subscribe'). It immediately distances itself from siblings by stating that the agent can skip the pitch and call evaluate_symbol, scan_bottoms, or scan_tops directly, so there is no ambiguity about which tool to pick.

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 says the tool is 'FREE and OPTIONAL' and instructs the agent that it may skip it and call the sibling tools directly. It also provides a concrete action for exiting the funnel ('Pass interest:false to bow out'), which fully resolves when and how to use the tool versus the alternatives.

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