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

With no annotations, the description carries the full burden of disclosing behavior, but it discloses none. It does not state whether this is a lookup, calculation, or whether it makes external calls, nor what output the agent should expect.

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 definition is extremely short, but this is under-specification rather than conciseness. The single phrase repeats the tool name and does not earn its place.

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 tool with two vague parameters, no annotations, and no output schema, the description is severely incomplete. An agent lacks enough information to call it correctly or interpret its result.

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?

Schema description coverage is 100%, so the baseline is 3. However, the description adds nothing beyond the schema's generic 'Year to process' and 'Input to process', leaving the meaning of 'input' and the expected format of 'year' unclear.

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 is 'Chinese New Year: Chinese New Year', which merely restates the tool name and provides no verb, resource, or action. An agent cannot determine whether this computes the date, zodiac animal, holiday facts, or something else.

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 given on when to use this tool or how it differs from nearby siblings such as x402-chinese-zodiac, x402-zodiac-sign, or date-related tools. There is no context for selection.

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