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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint=false, but the description adds real context: it explicitly states 'only reads and sends nothing to the vendor', documents that daily page views run oldest first, that the chart overlays price changes and upgrades, and that the share link is refreshed daily. It also notes the Cotlet API key access requirement. Only missing return-format specifics.

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?

Purpose is front-loaded and every sentence carries information (contents, ordering, share-link behavior, safety, auth). Slightly long at five sentences, with the dashboard-origin note being the least load-bearing, but no filler.

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?

No output schema exists, yet the description enumerates the returned fields and the share-link semantics, and it discloses auth prerequisites and read-only behavior. An agent has enough to call it correctly; only minor gaps (exact response shape) remain.

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?

With 100% schema coverage, the single listing_id parameter is fully documented in the schema ('Listing ID from list_listings'). The description adds no additional parameter meaning, so baseline 3 applies.

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 ('Get listing performance report ... for one property') and enumerates the exact contents: daily page views, price changes, Featured Properties upgrades, benchmark, share link. The 'for one property' scoping distinguishes it from account-level siblings like zoopla_get_performance_overview.

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?

Implies when to use it via the 'one property' scope and its origin in the ZooplaPro Dashboard, but never explicitly names an alternative (e.g. zoopla_get_performance_overview or zoopla_get_featured_properties_report) or states when-not to use it. Usage is inferable rather than spelled out.

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