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

Annotations already cover the read-only safety profile, and the description adds genuinely non-obvious behavior: each call consumes one of the plan's monthly export quota, and it requires a Cotlet API key with app access. That cost/auth context is exactly what annotations cannot express, though it says nothing about how the export is delivered.

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 core scope is front-loaded, but the definition restates itself: the 'Excel export... from Map Property Finder' idea appears twice, and the quota consumption ('Uses one of your plan's monthly exports' / 'Each call uses one of your plan's monthly exports') is stated twice. Trimming the repetition would tighten it.

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 should explain what an export tool returns (a link, a file, a job reference), and it does not. It is complete on scope, quota, auth, and presets, but the delivery/return side of an export operation is left unspecified.

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 coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: it explains the practical effect of omitting preset_id (all data vs. matching listings) and reiterates that neighborhood must include a city since city-only export is unsupported. The tab enum is explained in schema and description both, so credit is marginal but real.

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?

It states a specific verb+resource ('Excel export of a neighborhood from Map Property Finder') and scopes it tightly to one neighborhood and one tab. This distinguishes it from the property-level Mashvisor siblings (get_property_analysis, download_property_report), though it never names an alternative directly.

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?

It gives clear selection conditions ('Without preset_id it exports all data; with a preset it exports only the matching listings') and a hard exclusion ('City-level export is not supported'). It stops short of pointing to a sibling tool for property- or city-level needs, so it is clear context rather than explicit alternative routing.

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