calendar_week

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

No annotations are supplied, so the description carries the full burden. It does disclose the default behavior, but it does not state the date format returned, what happens if week exceeds the semester range, or that the boundaries follow the academic calendar rather than ISO weeks.

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?

One compact sentence with the returned value front-loaded and the default behavior attached. Nothing is wasted; the terseness is close to the minimum needed, though a brief note on return format would not be padding.

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 single optional-integer read tool with no output schema and no annotations, this covers purpose, result, and default adequately. Only the returned date format and out-of-range behavior are left unaddressed.

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 coverage is 100%, so the baseline would be 3, but the description additionally documents the default — omitting week yields the current teaching week — which the schema does not state. That is meaningful added semantics for the only parameter.

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 names a specific resource and result: the start and end dates of the Nth teaching week. It is clear what is returned, but it does not contrast itself with near siblings such as calendar_today or calendar_export, so an agent must infer the distinction.

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 parenthetical "缺省取当前周" implies when the parameter can be omitted and hints at the typical use case of getting the current week's boundaries. No explicit when-to-use or when-not-to-use guidance versus calendar_today or calendar_export is given.

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