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

Annotations already establish that this is a safe, read-only, closed-world operation, so the description does not need to restate safety. It adds meaningful behavior beyond the annotations: static.md has no key and cannot decrypt the note, and the response is a specific JSON format with encrypted Yjs updates, base64 IVs, AES-256-GCM ciphertext, and tags.

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 content is front-loaded and mostly tight, covering purpose, caller constraint, and response format in three sentences. The trailing 'Pro.' is unexplained and adds no value, which slightly hurts an otherwise efficient description.

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?

Although there is no output schema, the description thoroughly explains the return payload: JSON in static.md/e2e-note/v1 format with encrypted Yjs updates containing base64-encoded IV, AES-256-GCM ciphertext, and tag. An agent has enough information to call this correctly and understand what comes back.

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%, and the single id parameter is already well documented with its pattern and link-derived example. The description adds no further parameter syntax or semantics, which is an acceptable baseline when the schema carries this burden.

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 precise verb-and-resource framing: it returns the ciphertext of an end-to-end encrypted static.md note. It clearly distinguishes itself from the sibling read_note by emphasizing ciphertext and encryption, and it states up front that static.md cannot decrypt the content.

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?

It explains the intended caller: a program on the user's side that holds the key, such as the E2E bridge. That gives a clear context for use and implicitly routes plaintext-reading needs elsewhere, but it never explicitly names read_note or states when not to call this tool.

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