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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description usefully adds the auth requirement (Cotlet API key with app access) and the nationwide-when-unfiltered behavior, but says nothing about pagination or result volume.

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 opening two sentences are near-duplicates ('neighborhoods and cities ranked by rental performance, with your filters' repeated almost verbatim), which wastes space. The rest is efficient and front-loaded, but the redundancy is a clear flaw.

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 carries responsibility for describing returns; it says results are 'ranked by rental performance' but not what fields come back. Filters and the nationwide default are covered, and auth is mentioned, making it adequate but with a visible gap on return content.

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 baseline is 3. The description lists the filter dimensions (state, Mashmeter grade, min revenue, min occupancy, property types), but this largely restates parameters the schema already documents and adds no syntax or format detail beyond them.

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 clear verb+resource ('search ... markets'), and defines what a market is (neighborhoods and cities ranked by rental performance). It is distinguishable from siblings like mashvisor_find_properties or mashvisor_export_neighborhood_data, though it never explicitly contrasts with them.

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 one usage condition ('Without a state it searches nationwide') and enumerates which filters apply, which implies when the tool is useful. However, it never names an alternative or states when to prefer a sibling such as run_filter_preset or find_properties.

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