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

Annotations already convey readOnly, idempotent, and non-destructive behavior. The description adds useful behavioral context by explaining that possession of the listing id is what authorizes access, exactly as on the website. It does not describe the response format, but the stated state fields partially cover what the caller should expect.

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 compact and front-loaded: the first sentence states what data is returned, the second explains the id source and authorization, and the third gives usage guidance. Every sentence earns its place without 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?

For a single-parameter read-only lookup with strong annotations, the description is complete enough: it names the data fields, explains how to obtain and use the id, and routes to the relevant sibling. No output schema exists, but the first sentence effectively enumerates the key return values.

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 already documents the single listing_id parameter with a pattern and description, so schema coverage is 100%. The description's 'Takes the listing id from the listing URL' mostly restates the schema's 'part of a Duskly listing URL after /listing/,' adding little beyond the structured definition.

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 clearly states what the tool does: it returns the state of a Duskly listing, including photo counts, edit status, payment status, and render budget. It differentiates itself from the sibling duskly_get_listing_pack by positioning this as the precursor check for payment.

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 explicitly says 'Use this before duskly_get_listing_pack to check whether a listing has been paid for,' giving concrete when-to-use guidance against at least one sibling. It does not cover all sibling alternatives or provide explicit when-not-to-use cases, so it stops short of a 5.

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