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

Adds useful behavior beyond annotations: it opens a user-facing widget, imposes file size/type limits, and explains what happens after upload (transcription for audio/video, immediate readiness for text/PDF, no diarization). Annotations are not contradicted, and this context substantially helps set expectations.

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 sentences, all information-dense: the primary action comes first, followed by use-case guidance and post-upload behavior. No filler or repetition.

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 parameterless tool with annotations and no output schema, the description covers the action, the trigger conditions, file constraints, and behavioral outcomes. Nothing an agent needs to decide whether and when to call it is missing.

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 tool has zero parameters, so the description has no parameter documentation burden. The baseline of 4 applies; no schema or description gaps exist here.

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 names a specific action (opens the "Upload To Zernote" widget) and a specific resource (Inbox for this chat), and clarifies it is the usual ingest path in Claude. This clearly distinguishes it from the internal mcp_prepare/mcp_sign/mcp_confirm sibling tools.

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?

States exactly when to use it: when the user wants to upload/add an interview or get started on an empty account. It gives clear context but does not explicitly mention when not to use it or name alternatives for direct programmatic upload.

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