maimemo_create_note

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

Annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=true, so the safety profile is covered structurally. The description adds nothing on top: it does not mention that writes require the confirm=true authorization flag, does not explain the destructive impact, and does not note any idempotency 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?

It is a single short line with no waste, but its brevity stems from under-specification rather than disciplined conciseness. There is nothing front-loaded because there is almost nothing at all.

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 destructive mutation tool with nested objects and no output schema, the description is far too thin. It omits the confirm-gate requirement, the nested body.note structure, and the vocabulary-linking semantics, leaving the agent reliant entirely on structured fields.

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 all fields (voc_id, note_type, note, confirm) are documented in the schema, so baseline is 3. The description adds no meaning beyond the schema, which is acceptable here but not value-adding.

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 verb plus resource and is distinguishable from siblings like maimemo_create_interpretation or maimemo_create_notepad by the resource '助记'. However, it is bare-bones and gives no scope detail (e.g. that it attaches a mnemonic to a vocabulary id) beyond the name itself.

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?

There is no guidance on when to use this tool versus maimemo_update_note or the create_* interpretation/phrase siblings. The only implicit usage signal is the verb 'create', with no prerequisites or exclusions stated.

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