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

Annotations already declare readOnlyHint=true, and the description adds useful behavior: daily collection from three sources, duplicate merging, a 10-listing cap, and the requirement to show URLs. It does not cover pagination or rate limits, but adds meaningful context beyond the annotation.

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 three compact sentences, front-loaded with the core search behavior and followed by return details and a key display instruction. Every sentence adds useful information with no filler.

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?

Given 12 parameters, high schema coverage, and no output schema, the description adequately explains the search scope, data sources, return fields, and URL display requirement. It could say more about retrieving additional results beyond the 10-listing cap, but is otherwise complete enough for an agent to call 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 description coverage is high at 83%, so the schema already documents most parameters. The description mentions city scope and return fields but does not add parameter-specific meaning beyond what the schema provides, making baseline 3 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: "Searches active long-term rental listings" in a Bulgarian city, including data sources and deduplication. It is clearly a search tool, though it does not explicitly name sibling tools such as get_listing or get_price_stats to differentiate use cases.

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?

Provides clear context for when this tool applies: finding active long-term rentals in a Bulgarian city, with an explicit instruction to show each listing URL. It does not state exclusions or explicitly route to alternatives, so it falls short of full usage guidance.

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