zones_update_zone

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

With no annotations, the description carries full burden. It mentions that only passed fields are sent, indicating a partial update behavior. However, no details on side effects, permissions, or other behavioral traits are disclosed.

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 a single, clear sentence that immediately conveys the action and key behavioral note. No unnecessary words.

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 7 parameters, including optional ones like latitude, longitude, radius, etc., with no parameter descriptions. The description lacks constraints or valid ranges (e.g., lat/lon bounds, allowed icon strings). An output schema exists but is not explained. The description is too sparse for the complexity.

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?

The description adds minimal value beyond the schema property names. The phrase 'only the fields you pass are sent' clarifies behavior of optional parameters but does not explain individual fields. Given 0% schema coverage, more detail would be beneficial; borderline, but property names are self-explanatory.

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 clearly states the action 'Update' and the resource 'zone', with the specific endpoint. It distinguishes this as an update operation, but does not explicitly differentiate from sibling tools like 'zones_create_zone' or 'zones_delete_zone'.

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 description implies that only provided fields are updated, which gives usage context for partial updates. However, no explicit guidance on when to use versus alternatives (e.g., when to create or delete) is provided.

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