save_transcript

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

No annotations exist, so the description carries full burden. It discloses the output format (Markdown + JSON sidecar) but omits critical behavioral traits: whether it creates/overwrites files, naming conventions, required permissions, sidecar details, or error handling. 'Persist' is ambiguous.

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 a single sentence, which is concise and free of fluff. However, it could be restructured to front-load key operational details (e.g., 'Saves transcript to disk as Markdown...'). It earns points for brevity but lacks optimal structure.

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?

Given the tool's complexity (save operation, two params, no annotations), the description is too sparse. It does not mention file location, naming, behavior on existing files, or idempotency. The output schema exists but does not compensate for missing usage and parameter details.

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 input schema has two parameters (transcript, metadata) with 0% description coverage. The description does not explain what the transcript parameter should contain (e.g., text, object), nor what metadata is for. This is inadequate for an agent to correctly populate the arguments.

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 uses a specific verb 'persist' and identifies the resource as a transcript. It specifies the output format (durable Markdown plus JSON sidecar) and the target applications (Obsidian/Thorn). This clearly differentiates from sibling tools that focus on downloading or transcribing.

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 provides no guidance on when to use this tool versus alternatives (e.g., after transcribing, before uploading). It does not mention prerequisites, context, or conditions for use. The agent must infer usage from sibling names.

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