update_date_format

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

The description labels the tool as '[mutation]' indicating a write operation, but with no annotations, it fails to disclose side effects like scope (global vs per-session), reversibility, or required permissions.

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 sentence with a clear label, making it concise and front-loaded. No unnecessary words, but lacks structural elements like separate sections.

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 a simple one-parameter tool, the description is minimally complete. However, it omits behavioral scope and when to use it, which is relevant given similar sibling tools.

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 parameter is fully described in the schema (100% coverage) with enum values. The description merely echoes the parameter's purpose ('Formato de fecha') without adding extra context.

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 tool changes the date display format, using the verb 'Cambiar' and specifying the resource 'formato de fecha'. It distinguishes from siblings like update_timezone by focusing on date format rather than timezone.

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?

No guidance is provided on when to use this tool versus alternatives, such as update_timezone or other update tools. There is no mention of prerequisites or when not to use it.

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