Get Alt note transcript (incremental)

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

With no annotations provided, the description carries the behavioral burden. It discloses the incremental cursor behavior, token-saving intent, and first-call semantics. It does not address read-only safety or possible side effects, but the core behavioral contract is clearly described.

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?

Three short, focused sentences: purpose, incremental usage pattern, and initial-call handling. Every sentence earns its place and the most important usage detail is front-loaded.

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?

The tool has no output schema and no annotations, so the description must cover the operational loop, which it does by telling the caller to pass totalEntries from the last response. It is complete enough to call the tool correctly, though it does not describe the full response shape.

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 coverage is 100%, so the baseline is 3. The description adds genuine value by explaining how sinceIndex relates to the previous call's totalEntries and how to handle the initial call, going beyond the schema's per-parameter descriptions.

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 tool retrieves the real-time transcript of a note, which is a specific verb+resource. The incremental nature is also explicit, and this distinguishes it from siblings like get_note_info or list_note_components.

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 gives excellent practical usage guidance: pass the previous totalEntries to sinceIndex to get only new content, and omit or set to 0 on first call. It does not explicitly mention when-not-to-use or name alternatives, so it stops short of a perfect 5.

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