datetime_week_number

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

No annotations are provided, and the description does not disclose behavioral details such as return format, error handling, or edge cases (e.g., invalid date). It only states the purpose without clarifying the output structure or constraints.

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 sentence with no extraneous information. It is front-loaded and efficient, making it easy for an AI agent to parse quickly.

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?

Given no output schema, no annotations, and minimal parameter guidance, the description is incomplete. It does not inform the agent about the return value (e.g., integer 1-53) or how to handle invalid inputs, leaving significant gaps for a simple tool.

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% schema description coverage, the description must compensate. It merely implies the 'date' parameter is a date string but does not specify format (e.g., ISO 8601). The description fails to add meaning beyond the schema's empty property definition.

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 'Get the ISO week number for a date' uses a specific verb and resource, clearly indicating the tool's function. It distinguishes itself from sibling tools like datetime_date_diff or datetime_format_date by focusing on week number calculation.

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 computing ISO week numbers but provides no explicit guidance on when to use this tool versus alternatives (e.g., datetime_format_date). No to-not-use conditions or alternative tool references are given.

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