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 - and it discloses nothing: no output format, no return value, no explanation of how the reference date is anchored (e.g., current system date). For a zero-parameter tool, this ambiguity is severe because the agent cannot infer the tool's implicit behavior from any schema either.

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 brief, but this counts as under-specification, not conciseness - the same phrase is repeated twice with zero information content. There is no front-loaded signal that helps the agent understand or invoke the tool.

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?

With zero parameters, no annotations, and no output schema, the description is the sole source of guidance, and it is entirely vacuous. It fails to explain the operation, implicit input, output, or relationship to adjacent date utilities, making correct selection among thousands of siblings effectively impossible.

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 tool has zero parameters and an empty schema, so there is nothing to document per argument; per the rubric, zero-parameter tools get a baseline of 4. The only missed opportunity is that the description could have clarified the tool implicitly operates on the current date, which would have been useful 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 'Next Weekday: Next Weekday' is pure tautology - it restates the tool name twice without stating a verb, operation, or resource. An agent cannot determine what the tool actually computes, such as whether it returns the next weekday date relative to today or to a provided date, and nothing distinguishes it from the hundreds of sibling date 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?

No guidance is given on when to use this tool versus closely related siblings like x402-next-business-day, x402-prev-weekday, x402-add-business-days, or x402-weekdays-between. There is no context, no exclusions, and no alternative routing of any kind.

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