get_note_quick_note

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

No annotations are provided, so the description carries the full disclosure burden. It does add real value by disclosing the no-quick-note case ('明确返回不可用'), telling the agent not to treat an absent quick note as a failure. However, it says nothing about what a quick note contains, whether it is derived/synthesized, or the shape of the 'unavailable' response.

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?

A single front-loaded sentence plus one semicolon clause covering the failure case; no filler, no repetition of the tool name. Every clause contributes information.

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?

With no annotations and no output schema, the description must explain both side effects and return behavior. It covers the empty case but leaves the agent guessing about the normal return shape (text? structured object? timestamps?) and about whether this is a pure read with no side effects.

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%: the single `id` parameter is already documented as a note ID with a recommended decimal-string format. The description adds nothing about the ID beyond the schema, so the baseline 3 applies.

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?

States a specific verb (读取/read) and a specific sub-resource (录音笔记的快捷笔记, the quick note of a recording note), which meaningfully separates it from generic siblings like get_note, get_note_transcript, or get_note_original. It does not explicitly name or route against those siblings, so it stops short of a 5.

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?

Usage is only implied by the tool name and the 'quick note' sub-resource; the description never says when to prefer this over get_note or get_note_original, nor does it state prerequisites. The one useful signal is that the caller should expect an explicit 'unavailable' result rather than an error when no quick note exists.

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