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

Annotations only say readOnly=false and destructive=false, so the description carries the behavioral burden and succeeds: it reveals the async job flow (job_id, check_job_status, get_job_result), explains why the area cap is stricter (dense GeoJSON output), and warns the job cannot be canceled once submitted.

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 neatly divided into input, area limit, processing, output, flow, and pre-flight confirmation sections. Every bullet carries actionable information, and the most important scoping constraint is front-loaded near the beginning.

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?

For an asynchronous, high-cost analysis tool with no output schema, the description is unusually complete: it specifies required parameters, constraints, expected output format, polling/result retrieval, and the required preview/approval step. No critical call-time information is missing.

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 applies; the description largely mirrors schema details such as WKT format, date format, and sentinel-1 satellite_id. It adds a small amount of contextual meaning (max 5km² and area-splitting guidance), but no new parameter semantics beyond the schema.

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?

The description opens with a specific verb and resource: detects surface changes from Sentinel-1 SAR time-series data in a given area/period. The input/output sections make the scope concrete, and the time-series aspect distinguishes it from sibling object-specific analyzers like analyze_newbuilding and analyze_ship.

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?

The tool gives clear operating context: WKT polygon plus date range, a strict 5km² area cap with a split instruction, and a mandatory preview_analysis step with user approval before job submission. It does not explicitly name sibling analyzers to select instead, so it stops short of full when-not guidance.

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