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

With no annotations, the description carries the behavioral load and does well: it discloses the ~1 minute runtime, the $25 unlock cost, the watermark on the free preview, and geographic coverage limits (Florida and Indiana statewide, county by county elsewhere, aerial lower 48). Missing are any auth/permission requirements, failure modes, or whether regeneration is billed again.

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 capability and the address-vs-APN guidance are front-loaded, but pricing and plan details ("$25 gets the clean branded listing PDF... call get_pricing for what each plan includes") sprawl into a pitch that belongs in the pricing tool, and the free-PDF-preview sentence is convoluted.

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, and the description compensates by naming what comes back (a watermarked preview link and an unlock link) and the cost to unlock. For a creation tool with no annotations it is close to complete, though permission and re-run behavior remain unstated.

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. The description adds modest meaning beyond the schema – APN requires state and county, Florida resolves instantly and free, and asking_price floats on the 3D view – but most of this is already repeated in the per-field schema descriptions.

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 artifact: build a cinematic interactive 3D flyover listing from an address or APN, with the parcel boundary drawn on terrain. It also names the deliverable (preview link plus unlock link) and routes to get_pricing, so an agent can distinguish it from its siblings.

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?

Gives concrete when-to-use guidance ("raw land, acreage, odd lots, waterfront and new-construction dirt: anywhere a flat satellite photo undersells the property") and states an alternative path (a listing made on parcellaunch.com gets a watermarked PDF preview). It does not say when not to use it, e.g. whether an existing listing should be fetched via get_listing instead of regenerating.

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