append_to_periodic_note

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

With no annotations, the description carries the full burden, but it only says 'append content.' It doesn't disclose whether the note is created if missing, how formatting is handled, whether timestamps are added, or any permission requirements. There's no contradiction, but the behavioral disclosure is insufficient for a mutation.

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 with no fluff, which is appropriate for a simple tool. However, it's so terse that it leaves ambiguity about 'current' and behavioral details, making it slightly under-specified rather than genuinely concise.

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?

The tool is relatively simple with two parameters and no output schema, so the description is not drastically inadequate. Still, it could benefit from clarifying the current-note mechanism and append behavior, especially given sibling tools exist for other append targets.

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% with descriptions for both parameters, so a baseline of 3 is appropriate. The description adds the word 'current' but doesn't explain how the period enum maps to a specific note, nor does it add formatting or syntax details for content beyond the schema.

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 the action (append) and resource (periodic note), distinguishing it from append_to_file and append_to_active_file by the periodic-note context. However, 'current' is vague without explaining how the period parameter maps to a specific note, and it doesn't explicitly differentiate from get_periodic_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?

No guidance is provided on when to use this tool over siblings like append_to_active_file, append_to_file, or get_periodic_note. There are no exclusions, alternatives, or context clues about the intended workflow.

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