append_to_periodic_note

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only mentions the period targeting behavior, but fails to disclose other important traits such as whether the note is created if it doesn't exist, how content is formatted, or any side effects like timestamp changes. This is a significant gap for an append operation.

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 concise, with two short sentences that are front-loaded and free of fluff. The first sentence states the primary action, and the second adds a key scoping detail. It could be more informative, but it earns its place.

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 has 5 parameters, no annotations, and no output schema, the description is under-specified. It does not explain return behavior, edge cases like missing notes, or formatting of appended content. A more complete description would address these aspects, especially for a mutation tool with no annotation safety net.

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 description coverage is 100%, so all parameters are already documented in the input schema. The description's phrase 'current period's note or a specific date' reinforces the optional day/month/year parameters, but adds no new information beyond what the schema already says about defaulting to current values. Baseline 3 is appropriate.

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 verb 'Append' and the resource 'periodic note', and specifies that it can target the current period's note or a specific date. This distinguishes it from sibling tools like append_to_note and append_to_daily_note, which have different scopes.

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 implies usage for periodic notes and mentions the ability to target current or specific dates, giving some context. However, it does not explicitly state when to use this tool over alternatives like append_to_note or append_to_daily_note, nor does it provide exclusionary guidance. For comparison, the high example explicitly names an alternative.

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