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

Annotations mark readOnly=false, destructive=false, openWorld=true. The description adds context beyond them: it is reversible ('undone with remove_saved_home'), notification-free ('reaches no one'), and therefore safe to run without confirmation, plus it requires a Cotlet API key with app access. That is meaningful behavioral disclosure, though the auth phrasing is a bit oblique.

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-loaded and short, but the first two sentences are near-identical restatements ('Add a property to your Saved Homes' / 'Adds one property to your Saved Homes'), which is wasted space in an already compact description.

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 write tool with no output schema and annotations covering the safety profile, the description supplies purpose, reversibility, side-effect scope, and an auth requirement. An agent has enough to invoke it correctly; only explicit when-to-use guidance 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 coverage is 100% and the single property_id parameter is fully documented as coming from find_properties, run_filter_preset or list_saved_homes. The description adds nothing about the parameter, so the baseline 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?

States a specific verb and resource ('Add a property to your Saved Homes') and names the sibling that reverses it (remove_saved_home). An agent can distinguish it from the other saved-home siblings without opening the schema. However, the first sentence merely restates the title verbatim rather than adding information.

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 mention of remove_saved_home as its inverse implies this is the write half of a reversible pair, but there is no explicit guidance on when to prefer this over alternatives like find_properties or list_saved_homes, and no stated prerequisites for the property being valid.

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