publish_listingSubmit a draft listing for moderation review, making it eligible to go public once approved. This is an irreversible submission — confirm with the user before calling.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Listing ID to submit for review |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description discloses irreversibility, aligning with destructiveHint=true in annotations. Adds context that submission makes listing eligible for public approval, providing behavioral insight beyond 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?
Two sentences, no superfluous words. First sentence states purpose, second provides critical usage warning. Front-loaded and efficient.
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 simple tool with one parameter and no output schema, the description covers all necessary context: action, irreversibility, and confirmation requirement. No gaps.
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?
Schema coverage is 100% with one parameter 'id' documented. Description does not add extra parameter details beyond what the schema provides, meeting baseline but not exceeding.
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?
Clearly states the verb (submit) and resource (draft listing) and the purpose (moderation review for public eligibility). Distinguishes from sibling tools like close_listing or edit_listing.
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?
Explicitly states it is irreversible and requires user confirmation before calling. Provides clear usage guidance for a single-purpose tool, though no explicit alternatives are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have clearly distinct purposes, but there is some overlap between 'search' and 'search_listings', and between 'fetch' and 'get_listing'. However, descriptions effectively differentiate them.
Naming follows multiple patterns: verb_noun (create_listing), noun (closing_costs), get_*, search_*, my_*. While each pattern is internally consistent, the mix reduces overall consistency.
39 tools is relatively high, but they cover a broad set of real estate functionalities. The count feels slightly heavy but is justified by the domain scope.
The tool set covers the full lifecycle of listings (CRUD, promotion, sharing), account management, search with multiple filters, market data, guides, and lead management. No obvious gaps for the platform's purpose.