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, so the tool is safe and idempotent. The description adds behavioral details: uses hybrid search, gathers backlinks, optionally dailies, deduplicates, and packs to a token budget. It does not contradict annotations and provides useful process transparency beyond safety.

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?

Description is two sentences: first lists the step-by-step process, second explains the benefit. It is front-loaded, no filler, every sentence earns its place. Minimally viable length.

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?

Tool has 5 parameters, no output schema, but annotations are present. Description explains the overall flow and output (Markdown bundle). It does not detail exact composition of the output or mention default values for include_backlinks and recent_dailies, but given high schema coverage and no output schema, it is reasonably complete for an agent to understand usage.

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% (all parameters have descriptions). The tool description does not add new semantic meaning beyond the schema; for example, 'budget_tokens' schema already says 'Approximate token budget (default 4000, ~4 chars/token)' and the description only mentions 'token-budgeted' in the title. With high coverage, baseline is 3.

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?

Title 'Pack vault context for an AI question (token-budgeted)' and description clearly state the tool's purpose: given a question, retrieve top notes, gather backlinks and dailies, deduplicate, pack to a token budget, and return a Markdown bundle. It distinguishes from siblings like obsidian_search, obsidian_get_backlinks, and obsidian_read_note by combining multiple operations into one.

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?

Description says 'Saves the agent ~5 separate tool calls; produces a coherent context blob you can paste into any AI chat.' This implies use when you need compact context for an AI question, and that it replaces multiple separate calls. However, it does not explicitly state when not to use it or list alternatives.

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