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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds that the result includes moderation status, but it does not disclose return format, pagination, or error behavior. With the safety profile already carried by annotations, a 3 matches the calibration of simple read tools that lack richer behavioral context.

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 a single sentence with no filler or redundancy. The core action and resource are front-loaded, and every word contributes to the tool's meaning.

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, read-only tool with annotations covering safety, the description is largely complete for invocation. It names what is returned (listings and moderation status), though with no output schema it leaves the exact response shape unspecified. That is a minor gap, not a blocker for correct invocation.

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 input schema is empty with no properties, so there are no parameter semantics to explain. The description's phrase 'authenticated user’s own' clarifies that the data source comes from the auth context rather than an input parameter, which is sufficient given 0 parameters.

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 ('List'), a clear resource ('the authenticated user’s own listings'), and adds 'moderation status' to specify the output content. This clearly distinguishes it from sibling tools like list_my_favorites, list_my_requests, and search_rooms.

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 unambiguously scopes the tool to the authenticated user's own listings, so an agent can tell when to invoke it (e.g., 'show my listings') versus using a general search or another 'my' list. It does not explicitly name alternatives or exclusions, but the context is clear enough for selection.

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