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

There are no annotations, so the description must fully disclose behavior, but it fails to do so. It does not state whether the tool performs a side-effect-free conversion, what operations it performs on the provided parameters, or that most parameters are discarded. The description contradicts the schema by implying a simple conversion while the schema includes many unrelated fields, creating confusion.

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 extremely short, which could be seen as concise, but it lacks critical structure and information. Good conciseness means every word adds value; here, 'Juche year from UTC' is vague and does not earn its place. There is no front-loading of prerequisites or outcomes, and the brevity is not justified.

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 description is wholly inadequate for a tool with 10 parameters and no output schema. An agent cannot infer the correct usage, parameter selection, or expected return value. It does not explain the Juche calendar conversion algorithm, how to specify a date, or what the output looks like. This is a critical gap for effective agent invocation.

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 provides zero parameter information. Although the schema has 100% coverage with descriptions for each parameter, the tool's primary input (likely a date) is not even listed as a parameter. The many parameters like 'ref' and 'url' are irrelevant to a Juche year conversion, and the description does not clarify how any of them should be used or which one is required.

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 'Juche year from UTC' conveys a timezone conversion but fails to specify the output format, the exact meaning of 'Juche year', or the tool's actual functionality. It does not distinguish itself from sibling tools like 'utc-time' or 'timezone', and the large schema of unrelated parameters suggests the tool is a test or utility, not a straightforward date converter.

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. There is no mention of prerequisites, context, or exclusions. The tool name hints at a Juche calendar conversion, but the description is too terse to guide an agent on when to call it, especially given the many sibling tools.

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