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

Annotations already declare readOnly/openWorld/non-destructive, so the lower bar applies, and the description adds real context beyond them: each call consumes one plan-limited download, branded=true injects stored company name and logo, and a Cotlet API key with app access is required. It stops short of describing how the PDF is delivered back, so it is not exhaustive.

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?

Purpose is front-loaded, but the text repeats itself: the download-limit point appears twice ("Uses one download" / "Mashvisor limits downloads by plan, and each call uses one") and the branding behavior is stated twice as well. Tightening would remove roughly a third of the sentences.

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?

There is no output schema, so the description carries the burden of explaining the return, yet it never says whether the caller receives a URL, a file, or a stored report. Quota and auth are covered, but the result shape for a download-style tool 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 description coverage is 100%, so the baseline is 3. The description only restates the branded parameter ("company name and logo saved in your account") and adds nothing about property_id beyond what the schema already documents.

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: it produces a PDF analytics report for a property, optionally branded. That is clearly distinct from siblings like mashvisor_get_property_analysis (data retrieval) or mashvisor_export_neighborhood_data, so an agent can route to it without opening the schema.

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 hints at the trigger ("from the download icon on a property page") and notes the auth prerequisite, but never says when to prefer this over the analysis/comps siblings or what to do if downloads are exhausted. Usage is implied rather than stated.

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