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

Annotations already declare readOnly/openWorld/non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: pagination mechanics ('Pages hold up to 100 listings; pass next_cursor back as cursor') and an auth/permission requirement.

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?

Slightly padded and redundant: 'for Bayut or dubizzle' appears twice and the first sentence largely restates the title. The pagination and auth details earn their place, but the opening is not tightly 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?

With no output schema, the description usefully enumerates what each returned item carries (quality score colour, Checked/TruCheck badges, pending floor plan). Combined with annotations and full schema coverage, an agent has enough to call it correctly.

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 description coverage is 100%, so limit, cursor and platform are already documented; baseline is 3. The description only reinforces the page-size cap and cursor round-trip, adding marginal meaning over the schema.

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?

States a specific verb and resource ('Lists your listings') and describes the returned content (status, quality score, badges), which cleanly separates it from the read-one tool bayut_get_listing. However, it never explicitly distinguishes itself from other list-type siblings or names a condition that selects it over alternatives.

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?

Usage is only implied: you call it to enumerate your listings, and the platform param tells you it covers 'Bayut or dubizzle'. It adds the auth precondition ('Needs the user's Cotlet API key with access to this app'), but gives no when-not-to-use guidance or pointer to sibling tools.

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