notes

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

With no annotations, the description carries the full behavioral burden. It discloses the default return shape for list/search, but it does not mention that create is a mutation, whether it requires permissions or confirmation, or what side effects or output create has.

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 two tight sentences with the main purpose front-loaded and no wasted text. The retrieval behavior caveat is stated efficiently.

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?

There is no output schema, so the description needs to explain returns; it does so for list/search and full-text retrieval. It omits the return behavior for create and does not cover mutation side effects, leaving meaningful gaps for a four-operation tool.

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 the schema already documents all seven parameters, including operation enum values and required fields. The description reinforces the includeBody default and the get alternative, but it does not add meaningful syntax or format details 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 states specific verbs (search, retrieve, create) and the resource (notes in Apple Notes / Member Berries), so the core purpose is clear. It does not explicitly differentiate the tool from siblings such as briefing or reminders, but those siblings do not cover notes.

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?

It gives one useful usage rule: list/search return title and snippet by default, while includeBody=true or get retrieves full text. However, it does not explain when to choose search versus list versus create, so operation selection guidance is incomplete.

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