setup_aoi_monitoring

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It adds context about recurring monitoring and notification frequency, but does not disclose side effects such as creating persistent subscriptions, lifecycle management, or potential costs. It provides moderate behavioral insight but leaves gaps.

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?

Two tight sentences: the first names the action, the second clarifies usage. Information is front-loaded, with no redundant or filler words. It is appropriately brief while conveying necessary context.

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?

The tool has moderate complexity (4 params, nested AOI object, no output schema). The description covers the purpose, key configurable aspects, and a concrete usage scenario. It could also mention expected output or how to manage the monitoring, but given the schema fills in param details, the description is largely sufficient.

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 restates that sensor, resolution, and notification frequency are configurable, but does not add deeper semantics beyond what the schema already states. It reinforces the tool's purpose but offers no extra parametric detail.

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 uses a specific verb-resource pair ('Configure recurring monitoring of an AOI') and clearly specifies the domain (new imagery). It distinguishes this from sibling tools by focusing on ongoing alerting rather than one-time search or order, making its purpose unambiguous.

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 explicitly states the intended use case with 'Use this when the user wants to be alerted when new imagery becomes available over a specific area.' This gives clear context, though it does not mention when-not to use it or name alternative tools, so it stops short of a fully explicit exclusion/inclusion matrix.

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