Get current week

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

Annotations already mark it read-only and non-destructive. The description adds useful state context (status progression voting/selected/ordered/done, pending_feedback) but does not describe behavior such as whether week_id can target past weeks or any limits. No contradiction.

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?

Two compact sentences; the first front-loads the core purpose and content list, the second gives a crisp usage directive. No filler.

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 an output schema present, the return-value list is less critical, and read-only annotations cover safety. However, the optional week_id parameter is wholly unexplained, and for a tool meant to be called first, an agent needs to know whether passing week_id changes the result.

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 0%, and the description never mentions week_id. An agent sees the parameter name and type but not what it does, whether it overrides 'current,' or how it relates to 'latest week.' The description fails to compensate for the schema gap.

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 tool as the cycle-status snapshot: 'latest week + status (voting/selected/ordered/done)' plus the data it exposes (candidates, tallies, voters, selected recipes, pending_feedback). It lacks an explicit verb like 'gets' or 'returns,' but the content list and 'Call this first' make the purpose evident and distinguish it from action-oriented sibling 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?

Explicitly directs 'Call this first,' establishing this as the entry point before using other tools. It does not name alternatives or exclusions, but the 'first' directive gives enough context for an agent to sequence it correctly.

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