tz_add_conversion

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Add' implies a mutation, but the description does not state what files or systems are changed, whether an API key is required, whether the operation is reversible, or what side effects may occur. This is minimal behavioral information.

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 succinct, but it is under-specified rather than appropriately concise. 'Add timezone conversion' is a fragment that restates the tool name and provides no additional structured detail. It lacks the useful specifics that would make its brevity effective.

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 absence of annotations and output schema, the description is not complete enough for an agent to confidently invoke the tool. It does not explain what a timezone conversion addition involves, what output or effect to expect, or how api_key and directory are used. The tool's complexity is low, but the missing context still leaves critical gaps.

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 documents 'directory' with the description 'Project directory', but 'api_key' has no description, and the description itself adds no parameter meaning. With 50% schema description coverage, the description fails to compensate for the undocumented api_key parameter or explain how the parameters relate to the conversion being added.

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 states a clear verb and resource: 'Add timezone conversion'. It is a specific action on a specific feature, and the 'conversion' part distinguishes it from sibling tools like tz_setup_handling and tz_add_scheduling. However, it does not explicitly describe what the conversion entails or where it is added, so it is clear but not fully elaborated.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, whether a timezone setup must already exist, or how this differs from tz_add_scheduling or tz_setup_handling. An agent is left to infer usage from the tool name alone.

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