update_entry

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

Discloses partial update behavior, no-op for subject on notes, and behavior of timestamps (entryAt preserved, updatedAt advances only on actual changes). Annotations (readOnlyHint: false, destructiveHint: false) are consistent.

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 sentences, front-loaded with purpose and usage. Every sentence adds value; no redundant 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?

Description covers update behavior and constraints well. However, it does not mention the response format (e.g., returns updated entry). With no output schema, a brief note on what the tool returns would enhance completeness.

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?

All parameters have schema descriptions (100% coverage). Description adds context on partial updates and the no-op behavior for subject on notes, exceeding what schema provides.

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 'Edit an existing timeline entry — typically a note.' It specifies the action (edit/update), resource (timeline entry), and context (existing). Differentiates from sibling tools like 'delete_entry' and 'add_note'.

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 says to provide entry id and fields to change, notes that only supplied fields are modified, and warns that entry type cannot be changed. Suggests usage for correcting/extending notes. No ambiguity.

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