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

Beyond the annotations, the description adds important behavioral context: the listing remains unpublished, ownership belongs to the signed-in person, and publishing requires identity verification and photos. It openly states that publishing never happens here, which is valuable and not contradicted by annotations.

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?

Three short sentences front-load the core purpose and provide focused workflow details without any filler. Every sentence earns its place.

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 creation tool with no output schema, the description provides a clear end-to-end picture: draft creation, ownership, and the browser URL path for publishing. It does not detail all ten parameters, but the schema already documents some and the workflow is adequately scoped.

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 10 parameters and only 50% schema description coverage, the description adds no parameter-level meaning. It does not explain required fields, the meaning of bedrooms, bathrooms, square_feet, property_type, or description, nor does it compensate for the undocumented schema fields.

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 uses a specific verb ('Create') and precise resource ('unpublished draft rental listing'), and adds that it is owned by the signed-in person. It clearly distinguishes itself from a full publishing flow by stating 'Publishing is never done here.'

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 gives clear context: this tool only creates a draft and returns a URL to finish/publish in the browser. It explicitly excludes publishing, though it does not name a specific alternative sibling tool such as start_listing.

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