Get Notes

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

Annotations already indicate readOnlyHint=true, and the description adds crucial behavioral detail: notes are treated as secret output, value is null unless reveal=true and NOREVEAL is not active. This goes beyond annotations and clarifies an important aspect.

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 sentences, each contributing essential information without redundancy. It could be slightly more concise, but overall it is well-structured and front-loaded.

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 complexity (2 parameters, 1 required, 100% schema coverage, annotations, and an output schema), the description provides adequate context. It explains secret output behavior and search ambiguity, which is sufficient for correct invocation.

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% (both parameters have descriptions). The description adds meaning by explaining the reveal parameter's effect on secret output and ambiguity of terms, providing value 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?

Description clearly states 'Get item notes matched by bw get notes for a search term,' specifying the verb (get) and resource (notes). It distinguishes from siblings like keychain_get_item and keychain_get_password by focusing on notes retrieval.

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?

Description advises preferring exact item IDs when possible to avoid ambiguity, providing clear usage guidance. It does not explicitly mention when not to use this tool versus alternatives, but the context of siblings and the note-specific scope is evident.

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