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

Annotations already declare a safe read (readOnlyHint=true, destructiveHint=false), so the safety profile is covered. On top of that the description defines the non-obvious 'low performing' rule (lower click-through rate than similar listings) and states the auth prerequisite (a Cotlet API key with access to this app), which is real value beyond the annotations.

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 key facts (what it returns, the low-performing rule, filter behavior, auth need) are front-loaded and easy to scan. It loses a point for restating 'impressions, clicks and leads' twice in the opening two sentences, which is mild redundancy.

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?

There is no output schema, so the description carries the burden of describing returns and it does so adequately (per-listing impressions, clicks, leads). It also covers the auth prerequisite and the low-performing definition. It stops short of explaining pagination/cursor behavior, which matters for an 8-param list tool with a cursor.

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?

Schema coverage is 100%, so the baseline is 3 and the schema already documents every parameter. The description adds genuine semantics the schema lacks: filters are combinable, and the listing-ID filter ('reference') also accepts the user's own reference number, which changes how the agent should fill that field.

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 names the exact payload (impressions, clicks and leads per listing) and defines the low-performing concept, so the agent knows precisely what data comes back. It does not, however, contrast itself with nearby Bayut siblings such as get_traffic_report or get_market_insights, leaving the agent to infer which metric 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?

There is implicit guidance: use it when you want per-listing performance and can filter down to low performers, and 'filters combine' tells the agent it can stack criteria. But there is no explicit when-to-use/when-not-to-use statement and no named alternative, so routing against siblings is left to inference.

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