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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only the REST endpoint string and does not disclose the default time window, date_type filtering behavior, or pagination/return shape — the actual behavior an agent must anticipate.

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?

Two short sentences, front-loaded with the resource and the key conditional. Nothing is wasted, but the brevity comes partly at the cost of substance rather than purely from efficiency.

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 six parameters including a constrained interval window and a date_type enum, and no output schema, the description should explain the default time window and what a returned property record looks like. It does none of that, leaving the agent to rely entirely on schema prose.

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%, so every parameter (interval, date_type, fields, start_datetime, property_id) is already documented in the schema. The description merely restates the property_id behavior that the schema already explains, adding no extra meaning; 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 ('Properties a lead saved') and notes the single-item mode when property_id is passed. It is clearly distinct from siblings like idx_list_lead_searches or idx_list_lead_notes by virtue of the 'saved properties' resource, though it does not name those siblings explicitly.

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 parenthetical '(or one when property_id is given)' gives minimal selection guidance between the list and single-item forms. There is no statement about when to prefer this over other lead-related listing tools or any preconditions.

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