Inject Vault Summary

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the specific output content (categories, tags, priorities, notes) and the orientation purpose, but does not disclose additional behaviors like potential response size or vault resolution details. It adds moderate value beyond annotations.

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 three sentences, front-loaded with the main action, and each sentence provides meaningful information without redundancy. It is appropriately concise for the tool's simplicity.

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?

Despite the low schema coverage, the description covers the tool's purpose, the content of its output, and the appropriate usage context. With an output schema present and strong annotations, the description does not need to elaborate on return values or safety, making it complete for this straightforward tool.

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 0% for the single 'vault' parameter, and the description does not compensate by explaining the expected format (e.g., name vs. ID). The only hint is 'a vault's contents,' which is insufficient for a parameter lacking schema-level documentation.

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 generates a summary overview of a vault's contents and lists documents with categories, tags, priorities, and notes. However, it does not explicitly differentiate from sibling tools like vault_list_docs or vault_inject, relying instead on the phrase 'for conversation orientation' to imply its unique role.

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 provides explicit usage context by stating 'Useful at the start of a conversation,' which clearly indicates when to use it. It does not mention when not to use it or offer alternatives such as vault_list_docs or vault_inject_by_tag, but the usage guidance is clear.

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