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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so the bar is lower; the description adds real context beyond them by disclosing the per-artifact visibility semantics and that inline content is "bounded" and only readable for "your own or member-visible" artifacts, which implies an access restriction.

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 dense, front-loaded sentences with no filler; the return-shape summary comes first and the parameter guidance last. It is information-rich rather than padded, though the middle sentence packs several distinct concepts together.

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 sensibly describes the key returned fields, and with zero schema coverage it documents most parameters, so an agent has enough to call it correctly. Minor gaps remain around limit/pagination behavior.

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 carry the load, and it does for three of four parameters: clientRef (name or email), clientId, and includeContent (bounded inline content for note/markdown/html artifacts). Only limit is left unexplained (no default or pagination meaning), which keeps it short of a 5.

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 (List) and resource (professional artifacts saved to a member's X1 account) and enumerates the salient returned fields (visibility state, reviewUrl, promotedDocumentId). It is clearly distinct from document-search siblings, though it never names an alternative tool explicitly.

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 this to read back a just-saved draft and its promotion state" gives a concrete when-to-use scenario, which is more than implied usage. However it offers no exclusions or pointers to siblings such as get_vault_documents or search_my_documents for broader retrieval.

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