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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description discloses nothing — no side effects, no return behavior, no inputs, no context. It is completely vacuous.

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 short, but this is under-specification rather than conciseness. The few words present are wasted repetition of the tool name and 'Next Year' appears twice without conveying any meaning.

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?

Despite the tool having no parameters and no output schema (lowering the burden), the description is still completely inadequate. It provides zero information about what the tool does, what it returns, or when it should be invoked. An agent cannot use this definition to make any informed decision.

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?

With 0 parameters and 100% schema coverage, there are no parameters to document, so the baseline is 4. The description adds no semantic value, but there is no parameter information missing.

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 'Next Year: Next Year' is a pure tautology that restates the tool name without adding any verb, resource, or behavior. It does not say what the tool does — whether it calculates a next-year date, predicts the future, or something else entirely. It fails to distinguish from any of the hundreds of sibling tools.

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?

There is no guidance whatsoever about when to use this tool. No context, no conditions, no exclusions, and no mention of alternatives. An agent has no basis for selecting this tool over any of the sibling tools.

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