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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, and the description is consistent with them by stating the tool performs no action itself. It adds genuinely useful context beyond the annotations: the return is procedural guidance broken into screens, buttons and fields, and Bayut publishes no public API or API docs. The dated '(checked 12 Oct 2026)' note signals static, possibly stale knowledge, which is honest and helpful.

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 critical disclosure ('opens nothing by itself') is front-loaded, which is good. But the phrasing is dense and slightly awkward: 'from ChatGPT, Claude or any AI agent' is filler, and 'Bayut's official API: Bayut has no public developer API...' uses a label-colon construction that reads as a note pasted into a sentence. It is under-edited rather than bloated.

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?

With no parameters and no output schema, the description must explain what comes back, and it does: step-by-step screens, buttons and fields. It also explains the follow-up mechanism (cotlet_browser_* in the Cloud Browser) and the API absence that motivates this approach. The only gap is not describing the format of the returned steps or whether the guidance is static versus live-scraped.

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 zero parameters, so there is no parameter meaning for the description to add. The baseline for a 0-parameter schema applies, and nothing in the description misrepresents the 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 gives a specific verb and resource (list leads in the user's Bayut account) but immediately reframes it: this tool returns step-by-step instructions rather than lead data, and 'opens nothing by itself'. That reframing is essential and is stated explicitly, separating it from siblings like bayut_get_listing_performance or bayut_edit_listing, though the tool name alone would mislead an agent about what actually comes back.

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?

It states the usage path clearly: call this to get the Bayut steps, then execute them with cotlet_browser_* tools in the user's Bayut Cloud Browser. That is a concrete hand-off to the correct sibling family. It does not state any when-not-to-use condition or name an alternative for agents that want lead data directly, which keeps it out of the top band.

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