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

With no annotations present, the description carries the burden and does state 'Read-only' plus what content is returned, which is the key safety signal for a read tool. It does not cover failure modes (missing/invalid handle, cross-account access), which is the remaining gap.

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?

Front-loaded with the effect and the return contents, then usage guidance; every prose sentence earns its place. Deducted for the redundant 'Get Draft Detail' header and the stray '### Responses: 200' boilerplate, which add nothing and mimic an output schema that doesn't exist.

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 one-parameter read tool with no output schema, the description says what comes back and how to get the handle, which is close to sufficient. Missing only the failure/edge behavior an agent would want when a handle is rejected.

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 0%, so the description must compensate; it does so by naming the parameter, giving its expected format ('draft_ handle') and its source (from list_drafts). That is enough for correct invocation, though it doesn't describe error behavior for a bad or stale handle.

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?

States a specific verb+resource (get one connection-note draft's full detail) and enumerates the payload: full note text, the angle it was written from, and the addressed profile. It also explicitly contrasts with list_drafts previews, so an agent can pick between them without opening either schema.

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?

Gives two concrete trigger conditions ('user asks why a draft says what it says' or 'wants the full text') and names the alternative (list_drafts) plus why it is insufficient (it only previews). That is explicit when-to-use with the alternative surfaced.

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