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

With no annotations, the description carries the safety burden and satisfies it by labeling the operation as 'Read' and disclosing the auth requirement ('Requires your token'). It does not describe error behavior or return format, but for a simple vault get the core behavior is transparent.

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?

One concise sentence that states the operation and the critical auth requirement; no filler or unnecessary repetition of the tool name.

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 two-parameter, no-output-schema read tool, the description covers the main intent and auth, but it omits the role of the key parameter and does not address return/error expectations. This is adequate but leaves the agent to infer important retrieval semantics.

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 0% and the description only explains the token's role; it does not explain the 'key' parameter or how it relates to the stored value. The phrase 'previously stored' implies keyed retrieval but does not make the parameter semantics explicit.

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 ('Read') and resource ('value you previously stored in your fomite memory vault'), and its read semantics clearly distinguish it from sibling vault tools like fomite_vault_set, fomite_vault_create, and fomite_vault_list.

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?

It clearly signals this is for retrieving an existing stored value and tells the agent it must have its token available. It does not name alternatives or give explicit 'do not use when' conditions, but the read-vs-set/list context is clear from the tool family.

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