wb_note

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

There are no annotations, so the description carries the behavioral transparency burden. It does disclose that the domain contains write operations and that confirm is required, which is safety-relevant. It does not describe side effects, reversibility, or output behavior, but the explicit write/confirm warning provides meaningful value.

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 short and front-loaded with the domain and command family, followed by the confirm requirement. The parenthetical '（本域含写操作）' is mostly redundant with the preceding sentence, so it is not perfectly economical, but overall every other part 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?

For a generic command-family dispatcher with no annotations and no output schema, the description provides the core scope and the confirm gate, which is essential for safe invocation. However, it does not enumerate the full set of note subcommands or clarify the relationship with wb_note_add/wb_note_edit, leaving some context missing.

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 command, args, and confirm thoroughly. The description adds only the high-level note-domain context and the confirm requirement, which is already in the schema. This meets the baseline but does not add extra parameter-level detail.

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 a specific resource ('笔记域/note 命令族') and the operations it covers ('笔记列表/新增/编辑'), so an agent can tell it is the note-domain command tool. It does not explicitly contrast itself with the sibling tools wb_note_add and wb_note_edit, which slightly weakens sibling differentiation.

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 usage for note list/add/edit operations and gives a clear operational rule: write operations require confirm. However, it does not explain when to prefer wb_note over the more specific wb_note_add/wb_note_edit siblings, nor does it list exclusions or alternatives explicitly.

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