vault_stats

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

Full disclosure: describes output contents, deprecation status, and that it remains callable until v3.0.0. No annotations provided, so description carries full burden—no behavioral surprises.

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 plus deprecation notice, all essential. No wasted words, front-loaded with purpose.

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 tool with one optional param and no output schema, description is fully sufficient: covers usage, output, deprecation, and parameter 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?

Input schema has 0% description coverage, but description explains the 'vault' parameter: omit for all vaults, specify for a single vault. This adds essential meaning.

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?

Description clearly states verb ('overview') and resource ('vault'), and lists specific data points (note/word counts, top tags, etc.). It distinguishes from siblings like list_vaults and index_runs by focusing on statistical overview.

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?

Explicitly mentions deprecation and recommends an alternative MCP resource. Also explains behavior when 'vault' is omitted, giving clear usage guidance.

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