vault_status

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

Discloses the side effect of initializing the vault directory if needed, which is important. No annotations provided, so description carries full burden; it transparently describes the read-like behavior with a potential write side effect.

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?

Three sentences, front-loaded with purpose, then side effect and output, then definition. Every sentence adds value; no fluff.

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 zero parameters and presence of output schema, the description sufficiently covers purpose, behavior (initialization), and high-level output. No obvious gaps.

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?

No parameters, so baseline is 4. Description adds meaning by detailing the output contents (total beliefs, verification status, confidence distribution, routing statistics), going beyond the empty schema.

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?

Clearly states the verb 'Show' and resource 'state of CogOps Knowledge Vault', and elaborates on the specific output (coverage index, beliefs, verification, confidence, routing). Distinguishes from sibling vault tools like vault_query or vault_write_belief.

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?

Implicitly indicates usage for viewing vault state, but lacks explicit when-to-use or when-not-to-use guidance. Does not mention alternatives or exclusions, which would be helpful given many sibling tools.

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