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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe read-only operation. The description adds context about the source of related records (connector writes or Arkon Sync uploads), which is useful beyond annotations)Skip, but it doesn't describe potential behaviors such as record availability, ordering, or any retrieval limitations.

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 concise, two sentences, with no filler. The main purpose is front-loaded, and the additional detail on data sources is kept brief. Every sentence adds value without redundancy.

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 has only one parameter and no output schema, the description is adequate. It explains the tool's purpose and the nature of returned records. The main gap is the lack of guidance on when to use it compared to sibling tools like vault_get_context, but for a simple retrieval tool, the context is sufficient.

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 description coverage is 100% and explains the projectId parameter format with examples (grok:..., claude-code:...), so the schema carries the necessary detail. The description does not add parameter-specific information, so it relies on the schema; a baseline score of 3 is appropriate since the schema is sufficient.

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 clearly states the tool retrieves a project brief and related stored project records, with a specific verb ('Returns') and resource ('Arkon Vault project brief'). The scope is reasonably defined, but it could more explicitly differentiate from sibling tools like vault_get_context or vault_search_projects. The phrase 'Arkon Vault project brief and related stored session-derived project records' is specific enough to avoid confusion with generic tools.

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 implies the tool is for retrieving detailed project briefs, and mentions related records come from connector writes or separately approved Arkon Sync uploads, giving context on data sources. However, it does not explicitly state when to use this tool over alternatives like vault_get_context or vault_search_projects, or when not to use it. The context is present but not stated as direct guidance.

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