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

Annotations already disclose that the operation is non-read-only, destructive, non-idempotent, and open-world, so the description does not need to restate those safety traits. It adds useful scope by naming the server-side continuity index and the conditional Notion mirror, but it does not explain what data may be overwritten or what prerequisites are required for the mirror sync.

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 description is a single front-loaded sentence with no wasted wording. It puts the primary action and target first, then adds the conditional mirror scope.

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 zero parameters, no output schema, and annotations covering the safety profile, the description provides enough context to understand the operation's target and external side effect. It could be stronger if it clarified what "continuity index" refresh means operationally or noted prerequisites for the Notion mirror.

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 takes zero parameters, so parameter semantics are not a meaningful gap. The description appropriately avoids inventing parameter details, matching the empty input schema.

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 states a specific verb and resource: it refreshes the connected workspace continuity index on the server, including an optional Notion mirror. It is clear what the tool does, but it does not differentiate this operation from sibling tools such as vault_get_context or vault_preflight.

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?

The description explains what the tool refreshes but gives no explicit guidance on when to use it, when not to use it, or which sibling tool to choose instead. The Notion mirror clause is conditional scope, not usage guidance.

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