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

The annotations already establish that this is a safe, idempotent, non-destructive read with no open-world access. The description adds that the default response is the 'main smart note' while the alternate mode yields the full transcript, which is genuinely behavioral context. It is silent on what happens when the note is missing, how large a transcript can be, and whether transcript mode changes the response shape.

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 compact sentence with the primary action front-loaded and the alternate mode trailing. Every clause carries information, though it is arguably under-specified rather than optimally concise.

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 simple two-parameter read-only tool with an output schema, the description covers both operating modes. It omits failure behavior for unknown note IDs and any notion of what 'smart note' contains versus a transcript, leaving modest gaps for an agent deciding between modes.

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?

The schema already documents both parameters fully: note_id is '笔记 ID', and transcript is '是否返回转录'. The description's 'or return full transcript' restates the transcript flag's effect and adds the notion of a 'main smart note', but it gives no additional semantics such as transcript size, pagination, or fallback behavior. A baseline of 3 is appropriate given 100% schema coverage.

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 verb and resource (read the main smart note by note ID), and it also names a second mode (return the full transcript). This is clearly distinct from the list-style sibling notes_list, but it does not distinguish the tool from search. Overall, it is clear but not fully differentiated from siblings.

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 phrase "by note ID" implies that the tool is for known-ID lookup rather than discovery, and the transcript clause hints at when the alternate mode applies. However, the description never says when to use this tool versus search or notes_list, and it does not name any prerequisites or exclusions. The guidance is only implied.

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