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

Annotations already declare destructiveHint true and readOnlyHint false, so the description's 'creates or updates' aligns with that. However, it adds no extra behavioral context such as upsert semantics, duplicate handling, or side effects beyond the annotation signal.

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 encapsulates the action and key attributes, with no fluff. It is front-loaded with the primary purpose and reads clearly.

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?

Given the tool's straightforward purpose and full schema coverage, the description is reasonably complete. It would benefit from mentioning the unique behavior of using externalId/fromProjectId for updates, but that is already in the schema. No critical missing information prevents an agent from invoking it correctly.

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 100% with each parameter individually described. The description only reiterates a subset of fields (name, summary, platform, status, directory, link, external identifier) without adding any meaning beyond the schema. The baseline of 3 applies because the schema carries the full burden.

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 clear verb ('Creates or updates') and resource ('Arkon Vault project'), and lists the key fields involved. This immediately differentiates it from sibling tools like vault_get_project or vault_search_projects, which focus on reads.

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 implicitly conveys that this tool is for persisting project state, but it does not explicitly compare it to alternatives or state when not to use it. Since it is a write operation among many vault_* tools, an agent might infer usage, but no explicit guidance is given.

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