vaultpilot-mcp

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

With no annotations provided, the description carries full burden and delivers comprehensive behavioral disclosure. It explains the dual return behavior (pre-filled GitHub URL vs. proxy posting), clarifies 'NO data is transmitted' by default, documents detailed rate limits (30s between calls, 3/hour, 10/day), deduplication policy (7-day dedupe), and emphasizes human-readability requirements for summaries.

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 appropriately sized and front-loaded with the core purpose. Every sentence adds value: first states purpose, second provides usage constraint, third explains return behavior, fourth covers configuration variation, fifth documents rate limits, sixth emphasizes summary quality. Minor redundancy in 'clear, actionable' could be tightened.

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 no annotations and no output schema, the description provides exceptional completeness. It covers behavioral traits, rate limiting, configuration dependencies, usage constraints, and quality requirements. The only gap is explicit output format details, but the description adequately explains what the tool returns (URL or proxy post).

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 80%, so baseline is 3. The description adds value by emphasizing parameter importance ('Write clear, actionable summaries — this lands in a real issue tracker read by humans'), which provides context beyond the schema's technical specifications. However, it doesn't explain specific parameter relationships or provide additional syntax guidance.

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 specific action ('File a capability request') and target resource ('vaultpilot-mcp GitHub repository'), with explicit purpose to handle unsupported capabilities like protocols, chains, tokens, or missing tools. It distinguishes from sibling tools which are all operational tools for blockchain interactions, while this is a feedback/request mechanism.

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?

Explicit guidance is provided: 'USE ONLY AFTER confirming no existing tool can accomplish the task.' This creates clear when-to-use criteria and implicitly positions this as a last-resort alternative to all the operational sibling tools listed.

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