List Planner Notes

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

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower. The description does add one useful fact beyond annotations — that results are scoped to the caller's own notes — but says nothing about ordering, result volume, or pagination behavior.

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?

One short sentence, front-loaded with the verb and resource, zero filler. Nothing could be removed without losing 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?

For a low-complexity read tool with full schema coverage and no output schema, the definition supplies what is needed to call it. The only real gap is that it never positions itself against get_my_todo_items, leaving the agent to guess which one returns the to-do list it wants.

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% and covers defaults, formats, and the 366-day cap in detail. The description's "date window" framing merely echoes that; no parameter semantics are added 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?

States a specific verb plus resource ("List ... planner notes") and adds a parenthetical defining what a planner note is ("personal to-do items"). It does not, however, distinguish itself from the sibling get_my_todo_items, which could plausibly cover the same surface.

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 phrase "in a date window" implies the scenario for use, but there is no explicit when-to-use/when-not-to-use guidance and no named alternative despite get_my_todo_items and list_calendar_events being close neighbours.

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