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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds meaningfully: it scopes results to documents owned by the connected account, reports actual publication state and whether the URL is owner- or reader-facing, and flags that imported originals return only bounded file metadata while original bytes/HTML come from an authenticated embedded preview. That is substantive behavioral context beyond the structured fields.

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 usage, then return semantics, then the import/preview nuance; each sentence carries information. The final sentence is jargon-dense ("authenticated embedded preview handles original bytes and HTML source") and costs a little readability.

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?

With no output schema, the description takes on the burden of describing returns and does so: ownership scope, publication state, URL audience, and the import/preview distinction. An agent has enough to call it correctly and anticipate the 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?

Only one parameter and schema_description_coverage is 100%, so the schema already carries the meaning of id. The description adds a light constraint by saying the document must be owned by the connected account, but no additional syntax or sourcing detail beyond what the schema states.

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 (read/retrieve an existing SharedBrief document and its latest content/revision) and implicitly separates itself from list_documents and update_document by framing retrieval as a read step. An agent can tell this is a single-document fetch rather than a listing or mutation.

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?

"Use when the user wants to read an existing SharedBrief document or retrieve its latest content and revision before editing" gives a clear trigger plus a workflow context (pre-edit refresh). It does not name competing siblings such as read_document_for_app, read_document_file_from_app, or show_document, nor state exclusions, so no explicit when-not guidance.

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