practice_forecast

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

With no annotations, the description must fully disclose behavior. It states that the tool forecasts due memories and includes due times, implying a read-only operation. However, it does not explicitly confirm non-mutating behavior, output format, or any assumptions about the forecasting model.

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 that efficiently conveys both the action and the purpose. No unnecessary words or vague language.

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 the tool's simplicity (one parameter, no output schema), the description provides sufficient context: it states the core behavior and a typical use case. It does not detail edge cases or return format, but this is less critical for a straightforward forecasting 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?

The input schema has one parameter ('days') with zero description coverage. The description compensates by referring to 'the next N days', which implicitly maps to the 'days' parameter and provides its meaning. However, it does not specify constraints (e.g., default, minimum, maximum) or whether the parameter is required.

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 a specific action ('Forecast which memories are due within the next N days, with due times') and the resource (memories). It also includes the intended use case (plan a week of reviews), which distinguishes it from potential sibling tools like 'practice_report' or 'practice_plan'.

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 clear context for when to use the tool: to plan reviews ahead of time. It does not explicitly list alternative tools or exclusions, but the purpose statement effectively guides usage.

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