Create Note

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

Annotations (readOnlyHint=false, destructiveHint=false) already indicate a non-destructive mutation. The description adds behavioral context beyond annotations by stating that it 'returns a redacted item summary by default', which informs the agent about the output behavior without contradicting annotations.

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 concise sentences: first states the core purpose, second adds usage guidance and behavioral context. No redundant or extraneous information. Every sentence earns its 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?

Given the tool's complexity (7 parameters, 1 required), complete schema documentation, and clear annotations, the description adequately covers purpose, usage context, and key behavioral output (redacted summary). It could briefly explain 'redacted' but is sufficient for an agent.

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 7 parameters. The description adds no new parameter-specific details, but it does reinforce the purpose of custom fields and scoping. Baseline 3 is appropriate since the description does not extend parameter understanding significantly.

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 verb 'Create' and the resource 'secure note item', and explicitly distinguishes it from other creation tools by specifying it's for free-form text or secrets not belonging in login, card, identity, or SSH key items. This directly differentiates it from siblings like keychain_create_card or keychain_create_identity.

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 provides explicit guidance on when to use this tool ('for free-form text or secrets that do not belong in a login, card, identity, or SSH key item') and mentions what it accepts (custom fields, folder/organization/collection scoping). However, it does not explicitly state when not to use it or list alternative tools by name, though siblings are clear.

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