delete_property_listUse this when an authenticated user explicitly asks to permanently delete one of their PropFácil favorite lists and its saved entries. Do not use it for removing a single property.
| Name | Required | Description | Default |
|---|---|---|---|
| listId | Yes | Identifier of a favorite list owned by the authenticated user. |
| Name | Required | Description | Default |
|---|---|---|---|
| listId | Yes | ||
| deleted | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate destructiveHint=true, and the description reinforces permanence ('permanently delete') and the cascading effect ('and its saved entries'). It adds context about authentication requirement, which is not in annotations. No contradictions found.
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, front-loaded with a clear directive, and no wasted words. Each 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?
Given the tool's simplicity (1 parameter), strong annotations (destructive), and the presence of an output schema, the description is complete. It covers the essential usage and exclusions without needing additional details.
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 schema covers the parameter fully (description and constraints). The description adds the meaning of the parameter indirectly by mentioning ownership, but since schema coverage is 100%, the baseline of 3 is appropriate.
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 the tool deletes a favorite list and its saved entries, using specific verbs and the resource 'PropFácil favorite lists'. It distinguishes from sibling tools like 'remove_property_from_list' by explicitly saying not to use it for removing a single property.
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 provides explicit when to use ('when an authenticated user explicitly asks to permanently delete...') and when not to use ('Do not use it for removing a single property'). It also references the alternative tool implicitly by contrast.
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 a distinct resource-action pair, making selection generally clear. The main ambiguity is between get_property_list and list_property_lists, both of which involve favorite lists and could be confused by an agent despite different singular/plural meanings.
The majority of tools follow a snake_case action_noun pattern like search_properties, save_property_to_list, and rename_property_list. The exceptions are my_listings, which uses a possessive noun with no verb, plus get_property_contact and restore_property_results, which slightly break the otherwise consistent pattern.
Thirteen tools is a well-scoped set for a property search, listing publication, and favorite-list management server. Each tool supports a concrete workflow or user intent, with no obvious duplicated or filler tools.
The favorite-list workflows are reasonably complete, but there are notable lifecycle gaps: property listings can be published and searched but not updated, delisted, or deleted, and there is no explicit create-list operation for naming custom lists beyond the default behavior. This creates awkward workarounds for some common user requests.