Set Writing Goal

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

The description explains that setting a goal of a type that already has an active goal updates in place rather than stacking duplicates, which goes beyond the destructiveHint annotation. It also notes the requirement for a project database. No contradiction with annotations.

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?

Three well-structured sentences, each adding value: purpose+behavior, usage guidelines, and related tools/requirements. No extraneous information.

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 tool with no output schema, the description sufficiently covers behavior (updates in place), preconditions (requires project database), and related tools. It is complete and actionable.

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 baseline is 3. The description adds meaningful context for each parameter: explains the behavior of 'type' cadences, the purpose of 'targetDate' for pacing judgment, and that 'targetWords' is a positive whole number.

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 it creates or replaces an active word-count goal for a cadence (daily, weekly, or project) with optional target date. It uses specific verbs and resource, and distinguishes from siblings like get_writing_goals and predict_completion.

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?

Provides explicit when-to-use ('when the writer commits to a target') and when-not-to-use ('not when you only want to read current progress... or log a finished session'), and names alternative tools (get_writing_goals, predict_completion).

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