vault.info

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

No annotations are present, so the description carries the full burden of behavioral disclosure. The description states 'Get statistics' implying a read-only operation, but it does not disclose any potential side effects, authentication requirements, rate limits, or other behavioral traits. For a simple read operation, the lack of explicit transparency is a gap.

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 a single sentence, concise and to the point. It contains no extraneous information. However, given the tool's simplicity, some additional context could be added without losing conciseness.

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?

With no output schema, no annotations, and an undocumented 'vault' parameter, the description is insufficient for an AI agent to fully understand the tool's usage and behavior. It provides only the bare minimum of what the tool does, leaving significant 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?

Schema description coverage is 50% (only '_budget' has a description). The tool description adds no extra meaning for the 'vault' parameter, leaving its format or semantics unexplained. The description does not clarify what 'vault' refers to (e.g., name, ID), failing to compensate for the missing schema 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 verb 'Get' and resource 'statistics for a single vault', distinguishing it from the sibling tool 'vault.list' which lists vaults. However, it does not specify what kind of statistics are returned, such as size or item count, limiting specificity.

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?

No usage guidelines are provided. The description does not indicate when to use this tool versus alternatives like 'vault.list'. The context implies that this is for obtaining stats for a known vault, but no explicit when-to-use or when-not-to-use guidance is given.

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