update_timezone

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

The description tags the tool with '[mutation]' indicating state change, but there are no annotations to supplement. It does not disclose potential side effects, permission requirements, or what happens after the timezone is updated. For a mutation tool with no annotations, more behavioral context is needed.

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 very short and to the point. It includes a useful [mutation] tag. However, it is sparse and could be expanded briefly without losing conciseness.

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?

Given the simple tool (one parameter, no output schema), the description is minimally adequate. It explains the purpose and parameter format. However, it lacks details on scope or confirmation of the change.

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 schema already describes the parameter with format guidance (IANA). The description adds no extra meaning beyond restating the purpose. With 100% schema coverage, baseline is 3, but the description fails to add value, hence a lower score.

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 'Cambiar zona horaria' (change timezone) and explains the purpose: to display dates and times correctly. It is a specific verb with a specific resource, and no sibling tool directly overlaps.

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 when to use it (when timezone display is incorrect), but provides no explicit guidance on when not to use it or mention of alternatives (e.g., update_date_format is a sibling). No usage context is given.

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