Append to periodic note

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

Annotations are all false, so description carries burden. It discloses heading creation behavior and settings dependency. However, it does not specify idempotency, order, or error cases, leaving gaps.

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 sentences convey all essential info without fluff. Front-loaded with the action, then context.

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 mutation tool with no output schema, the description covers key aspects: action, resource, parameter behavior, and settings dependency. Minor gaps (e.g., no mention of return value) but overall adequate.

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 covers 100% of parameters, but description adds value: explains that folder/format come from settings (not parameters) and elaborates on heading behavior (created if missing).

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 an entry') and the resource ('daily, weekly or monthly note'), and distinguishes from siblings like 'append_to_daily_note' by covering all periods. It also notes heading creation if missing.

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 does not explicitly guide when to use this tool versus alternatives like 'append_to_daily_note'. It implies broader applicability but lacks direct comparison or exclusionary context.

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