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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that: which fields are returned, that entries come from analyze_unlisted_property or save_home, and that a Cotlet API key with app access is required. No rate limits or pagination behavior are described, keeping it below a 5.

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 are near-verbatim restatements ('Properties in your Saved Homes, with type, sale price and your rating' vs 'Returns the properties in your Saved Homes with type, sale price and your rating'), wasting a sentence. The useful information (provenance, downstream tools, auth) is present but not front-loaded.

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?

With no output schema, the description correctly takes on the burden of describing return values (type, sale price, rating) and the auth requirement. It leaves pagination/ordering behavior for the limit param unspecified, but is otherwise complete for a simple read-list tool.

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?

Only one parameter (limit) and schema coverage is 100%, so the schema already documents its range and default. The description adds no syntax or semantics beyond that, which matches the baseline 3 when the schema does the work.

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 (list properties in Saved Homes) and enumerates the returned fields (type, sale price, rating). An agent can distinguish it from siblings like get_property_analysis or 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?

Explicitly routes the returned property_id into get_property_analysis, get_property_comps, or remove_saved_home, giving a clear downstream flow. It does not state when this tool is preferred over other listing/analysis tools or any exclusions, so it stops short of full when/when-not guidance.

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