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

Annotations already mark this as read-only, idempotent, and non-destructive. The description adds valuable behavioral context beyond those annotations: default open-only, ordering by oldest stage-change, and concrete cold thresholds per stage. It does not contradict the annotations.

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 description is compact at two sentences with no filler, and the default/ordering behavior is front-loaded. The opening phrase 'Deals with property and contact context' is vague and could be clearer, but overall the structure is efficient.

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 5-parameter list tool with no output schema, the description covers defaults, ordering, and cold semantics, but it leaves ambiguous what 'property and contact context' means in the response and does not mention how to request closed deals via openOnly=false or pagination via limit. The schema covers the filters, so this is adequate but not fully complete.

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 80%, so the schema carries most parameter meaning. The description adds the cold/stage-threshold concept, which helps clarify stage semantics, but it does not explain limit, source, or ownerAgentId beyond what the schema already provides.

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 title supplies the verb ('List deals') and the description adds scope ('with property and contact context') plus default filtering and ordering behavior. However, the first sentence is phrased ambiguously and the tool is not explicitly differentiated from get_deal or other list tools.

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 gives default behavior but no when-to-use guidance or alternatives. It never states when to prefer this over get_deal for a single deal, or over list_properties/list_contacts for those entities, and there are no exclusions or routing conditions.

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