Pack vault context for an AI question (token-budgeted)

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds significant context: token-budgeted, deduplication, hybrid search, and output format (markdown bundle). No contradictions.

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?

Two sentences with key information front-loaded. Very concise, but could benefit from breaking into a short list for even better readability.

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 5 parameters and no output schema, the description adequately explains the overall process and return format. It covers the main behavioral aspects but lacks details on error handling or edge cases.

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 has 100% coverage with descriptions for all 5 parameters. The description adds minimal extra meaning: it mentions 'hybrid search' and 'token budget default 4000', but the schema already explains defaults and types. Baseline 3 is appropriate.

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 specifies a specific verb ('retrieve', 'gather', 'pack', 'return') and resource ('context pack for an AI question'). It clearly distinguishes from sibling tools like obsidian_search or obsidian_get_backlinks by describing it as a composite that replaces ~5 separate calls.

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 states when to use (when needing a ready-to-paste context blob) and implies it's an alternative to multiple manual calls. However, it does not explicitly list exclusions or when to avoid using it, leaving some ambiguity.

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