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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine context beyond them: it discloses the auth requirement ('Needs the seller's sign-in') and the fact that each record carries an activate_url the seller opens to post, which is a behavioral detail not derivable from any structured field. It stops short of pagination, ordering, or behavior when no drafts exist.

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?

A single compact sentence with the resource front-loaded, followed by the return fields and the auth caveat. No filler and nothing redundant with annotations or schema.

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 present, the description usefully enumerates the returned fields and adds the sign-in prerequisite, which is enough for an agent to invoke a zero-parameter read correctly. Minor gaps remain around result volume/ordering and the empty-drafts case.

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 the baseline is 4; there is nothing for the description to clarify beyond the implicit seller scoping, which it does convey ('the seller's drafts').

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 names the specific resource ('The seller's drafts') and enumerates the returned fields (id, title, last saved, activate_url), so an agent knows exactly what it retrieves. It does not, however, distinguish itself from the adjacent ingatlan_draft_fields or ingatlan_how_to_post siblings, which an agent could plausibly confuse with a drafts-listing call.

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: the phrase 'the seller's drafts' and the activate_url mention suggest the pre-publish workflow, and the sign-in note establishes a prerequisite. There is no explicit statement of when to call this versus ingatlan_draft_fields or ingatlan_search_listings, and no exclusions.

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