week_number_calculator

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

The description lacks behavioral details beyond the basic operations. It claims to also accept week numbers, but the input schema only has a 'date' parameter, creating confusion. No annotations exist to compensate. Default behavior (today) is not stated.

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 a single, efficient sentence that front-loads the core functionality with no extraneous words.

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 tool has two distinct functions but the description does not explain how to specify a week number to get its date range. No output schema or return value description is provided, leaving the agent uncertain about results.

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?

Although schema coverage is 100%, the description introduces ambiguity by implying the tool accepts week numbers while the schema only documents a date parameter. This mismatch detracts from clarity. Baseline 3 is not warranted due to the confusion.

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 states the tool finds ISO week numbers for a date and the date range for a week number, with specific verb and resource. It distinguishes from sibling tools like date_calculator which likely handle general date arithmetic.

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 implies usage for ISO week numbers and week date ranges but does not specify when not to use it or mention alternatives among siblings. No explicit exclusions or context provided.

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