get_periodic_note

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

No annotations are provided, so the description carries the disclosure burden. It reveals that the Periodic Notes plugin is required for non-daily periods, which is useful context. However, it does not state whether the operation is read-only, what happens if the note does not exist, or the return format, leaving gaps in behavioral transparency.

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 consists of two concise sentences with no redundancy. The first sentence states the purpose, and the second adds supported periods and a dependency caveat, both earning their 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?

The description covers the tool's purpose and key dependency. The schema handles parameter descriptions and defaults. Missing details about return value or error behavior are minor for this simple getter tool, especially given the absence of an output schema.

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 descriptions cover all 4 parameters (100% coverage), so baseline is 3. The description adds the plugin requirement for non-daily period values, which provides additional semantic context for the 'period' parameter beyond the enum list in 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 begins with a specific verb and resource: 'Get a periodic note for a specific period and date.' It explicitly lists the supported period types (daily, weekly, monthly, quarterly, yearly), distinguishing it from sibling tools like get_daily_note which is daily-only.

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 this is the general tool for all periodic notes but does not explicitly compare it to get_daily_note or state when to prefer one over the other. It does note a plugin requirement for non-daily periods, giving some usage context, but lacks explicit alternatives or exclusions.

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