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

It discloses meaningful behavioral boundaries: no local file access, no ability to start Arkon Sync, and no uploading of conversations. The annotation set already covers read-only/idempotence/destructive traits, so the description adds context without contradiction.

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 two crisp sentences. The first names the action and targets; the second clarifies limits and the alternative for uploads. Every phrase adds value.

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 parameterless tool with no output schema, the description gives enough operational context: what it refreshes, that it is server-side, and what it cannot do. It does not state success/error behavior, but that is not necessary at this level.

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 input schema has no parameters, so the 100% schema coverage is trivially complete. The description does not need to explain parameters and does not clutter the definition with them.

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 specific verb ('Refreshes') and identifies the exact server-side objects affected: the Arkon Vault continuity index and any configured Notion mirror. It also distinguishes this action from local sync and upload behavior by explicitly stating those are out of scope.

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 clearly states what the tool cannot do and points to Arkon Sync as the separate tool for uploads, which gives useful when-not guidance. It does not explicitly compare this tool to sibling vault_* tools, but the 'refresh server-side index' purpose is enough to separate it from handoff/project tools.

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