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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds meaningful context beyond those annotations: it clarifies that the tool returns instructions only, opens nothing by itself, and that Bayut has no public API. This helps an agent understand the tool is a guide, not an action.

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 front-loaded with the core behavior and is reasonably concise. Some phrases, such as 'from ChatGPT, Claude or any AI agent' and the repeated API note, are slightly redundant, but they do not obscure the main point.

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 guide tool with no output schema, the description is complete enough: it explains what is returned (step-by-step screens, buttons, fields) and that the tool does not act on its own. It could be improved by explicitly naming when to prefer it over sibling Bayut tools, but the essential context is present.

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 has zero parameters, so the baseline is 4. The description does not need to explain parameter semantics, and the empty schema is consistent with a no-argument instruction tool.

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 states a specific verb and resource: it returns step-by-step instructions for refreshing a Bayut listing rather than performing the refresh itself. It distinguishes itself from the cotlet_browser_* tools by saying it opens nothing and must be followed by browser actions, but it does not explicitly differentiate from sibling Bayut tools like bayut_edit_listing or bayut_publish_listing.

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 implies a workflow: use this tool to get instructions, then execute them with cotlet_browser_* tools. However, it gives no explicit when-to-use or when-not-to-use guidance relative to other Bayut tools, and no prerequisites or exclusions are stated.

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