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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true) by disclosing that no confirmation prompt occurs, that nobody is notified, that the removal also affects the containing collection, that save_home reverses it in one call, and that a Cotlet API key with app access is required. This is rich behavioral and auth context.

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?

Front-loads the core action and is compact, but the opening phrase restates the title and the removal is described twice ('Remove a listing from your saved homes' then 'Removes a listing from your saved homes...'), a minor 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 mutation with no output schema, the description covers the action, side effects, reversibility, confirmation behavior, and auth needs. It is essentially complete; only a strong explicit when-to-use trigger is missing.

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 description coverage is 100% and the sole parameter (listing_id) already documents its source ('from search_listings or list_saved_homes'). The description adds no further parameter detail, so the baseline 3 applies.

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?

States a specific verb and resource ('Remove a listing from your saved homes') and adds scope detail ('and from its collection'), which distinguishes it from siblings like save_home, list_saved_homes, and list_collections. An agent can identify the operation without opening the schema.

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?

Names the inverse operation explicitly ('save_home undoes it in one call'), which routes the agent when a user reverses course, and signals it 'runs without asking' so no confirmation is needed. It stops short of stating an explicit when-to-use trigger, but the context is clear.

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