vaultpilot-mcp

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

With no annotations provided, the description carries full burden. It discloses the return behavior ('Returns null if no primary name is set'), which is valuable. However, it doesn't mention rate limits, authentication needs, or other operational constraints that would be helpful for an agent.

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 two concise sentences with zero waste—front-loads the purpose and adds crucial behavioral detail about null returns. Every word earns its place without redundancy.

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 single-parameter tool with no annotations and no output schema, the description is adequate but minimal. It covers the core purpose and return behavior but lacks details on error cases, performance, or integration context that would help an agent use it effectively.

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 0%, but the description doesn't add parameter details beyond what's implied by the tool name. The single parameter 'address' is clear from context, but the description doesn't explain the dual pattern (Ethereum vs Tron addresses) shown in the schema, leaving a gap.

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 ('reverse-resolve'), target resource ('Ethereum address'), and outcome ('to its primary ENS name'), with explicit mention of the null return case. It distinguishes from sibling 'resolve_ens_name' by indicating the opposite direction of resolution.

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 implies usage context by specifying 'primary ENS name' and the null return condition, which helps differentiate from 'resolve_ens_name' (forward resolution). However, it lacks explicit guidance on when to choose this tool over alternatives or any prerequisites.

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