Update Objective

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

Describes that omitted fields are unchanged, null clears description/period, and returns the objective. Complements annotations (idempotent, non-destructive) with specific behavior.

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 concise sentences, front-loaded with action and key details. No wasted words.

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?

Covers purpose, parameter semantics, and usage, but lacks explicit description of return structure (beyond 'return it'). For a simple update tool, it suffices; could add detail on return format.

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?

Adds meaning beyond schema: explains null vs omission behavior for description and period. Schema descriptions are present but the description clarifies semantics crucial for correct usage.

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?

Clearly describes updating an objective's name/description/period, with specific verb and resource. Distinguishes from sibling update_key_result.

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 states when to use (update objective) and when not (move key result use update_key_result), and instructs to resolve id via list_objectives.

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