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

Annotations declare destructiveHint=false and readOnlyHint=false, and the description adds real context beyond them: the action notifies no one, is reversible ('can be added again with save_home'), runs without confirmation, and requires a Cotlet API key with app access. No contradiction with annotations; the reversibility and auth disclosure are genuine value-adds.

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?

The first two sentences restate the same fact ('Remove a property from your Saved Homes. Removes one property from your Saved Homes.'), which is pure redundancy. The remaining behavioral and auth sentences are efficient and front-loaded, so it is decent but not tight.

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 one-parameter, no-output-schema mutation, the description covers purpose, reversibility, notification behavior, confirmation stance, and auth requirements. Nothing critical is missing, though the redundant opening sentence and absent precondition slightly dilute it.

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% and the schema already documents property_id including its source tools (find_properties, run_filter_preset, list_saved_homes). The description adds no 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+resource ('Remove a property from your Saved Homes') and implicitly contrasts with the sibling save_home, which it names as the way to re-add. An agent can distinguish this from list_saved_homes and save_home without opening any 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?

Usage is implied rather than stated: it names save_home as the recovery path, which helps orient the agent, but there is no explicit when-to-use vs alternatives guidance or a statement of the precondition (the property must already be saved). Adequate but thin.

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