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

There are no annotations, so the description carries the full behavioral burden. It only restates the basic operation and does not disclose whether weekends and holidays are skipped, whether negative day counts are supported, or what date formats are accepted.

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 text is short, but the leading 'Add Business Days:' repeats the tool name and the remaining phrase simply restates the same operation. It is concise but does not use its brevity to add meaningful structure or extra value.

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 3 params, no annotations, and no output schema, this description is insufficient. It does not clarify required inputs, date format, holiday handling, return value, or how it differs from the many adjacent date utilities in the sibling list.

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 even though the parameter descriptions like 'N to process' and 'Days to process' are generic and unhelpful. The tool description itself adds no meaning about which parameter is the start date versus the count.

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 clearly identifies the operation: adding business days to a date, with a specific verb and resource. It also implies some distinction from sibling date tools like x402-add-days by specifying 'business days', though it does not elaborate on what defines a business day.

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 close siblings like x402-add-days, x402-next-business-day, or x402-weekdays-between. There are no conditions, exclusions, or alternative tool references.

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