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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description goes beyond that by explaining the paused state (cannot be booked, hidden from search, guests cannot contact you) and the auth requirement ('Needs the user's Cotlet API key with access to this app'), which the structured fields do not convey. It stops short of pagination/rate-limit detail, but 'returns every listing' implies the full set.

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?

Front-loaded with the resource and return shape, and every sentence carries information. The first and second sentences overlap heavily ('with base rate, Instant Book and paused status' restated as 'with its space, base rate, whether Instant Book is on'), a minor redundancy that keeps it from a 5.

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, no output schema and annotations covering the safety profile, the description supplies the remaining essentials: the fields returned, the operational meaning of the paused flag, and the API-key prerequisite. Nothing an agent needs to invoke it correctly is missing, though the overlapping restatement means it is not maximally tight.

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 nothing for the description to disambiguate; the baseline for a no-param tool applies. The description correctly frames it as an unfiltered account-wide listing.

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 ('List listings') and immediately scopes it to 'your host account', so the agent knows it returns the caller's own listings rather than a marketplace search. The return contents (space, base rate, Instant Book, paused status) are named up front, making it easy to distinguish from siblings like peerspace_get_calendar or peerspace_list_bookings.

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?

Gives clear context for when to reach for this tool (enumerating your own listings and grabbing their IDs) via 'Use the IDs here in the other calls', which signals it is a discovery/entry point. It does not name an alternative or a when-not condition, but there is no true sibling that lists host listings, so the omission is minor.

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