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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is established. The description adds that the result is shared context including projects and handoffs for the current workspace, which is modest behavioral context, but it does not describe response structure, filtering behavior, or any operational constraints. This is acceptable for a read-only, zero-parameter tool but not exceptional.

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 sentence that front-loads the action and resource, then adds the two key content categories and scope. Every phrase contributes useful information with no wasted words.

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 zero-parameter, read-only tool with annotations covering safety and idempotence, the description covers the essential return content ('projects and handoffs') and context ('connected workspace'). It is slightly vague about what 'context' includes beyond those two categories and does not detail the output shape, but the lack of parameters and output schema makes this a minor gap.

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 there are no parameter semantics for the description to clarify. The baseline for zero-parameter tools is 4, and the description does not introduce any confusion or conflicting parameter expectations.

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, 'Returns,' names the resource ('shared Arkon Vault context'), and specifies contents ('projects and handoffs') and scope ('connected workspace'). It is clear about what the tool does, though it does not explicitly differentiate itself from siblings like vault_get_project or vault_list_handoffs, so it stops short of a 5.

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 gives no guidance on when to use this tool versus the many sibling tools, such as vault_get_project, vault_list_handoffs, or vault_list_conflicts. An agent can infer that this returns an aggregate overview, but the description never states that or provides exclusions or alternative routing.

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