vaultpilot-mcp

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

With no annotations provided, the description carries full burden but only lists what is checked without disclosing behavioral traits. It doesn't mention whether this is a read-only operation, potential rate limits, authentication needs, error conditions, or what the output format might be. The description is informative about scope but lacks operational transparency.

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, well-structured sentence that efficiently lists all security checks. It's front-loaded with the main purpose and contains zero redundant information. Every clause earns its place by specifying a distinct aspect of contract security analysis.

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?

Given the tool's complexity (security analysis with multiple checks), no annotations, and no output schema, the description is incomplete. It specifies what is checked but doesn't cover how results are returned, error handling, or operational constraints. For a security analysis tool with 2 parameters and significant functionality, more context would be helpful.

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%, so the description must compensate. While it doesn't explicitly name parameters, it strongly implies the 'address' parameter (contract to check) and contextually suggests 'chain' (supported blockchain). The description adds meaningful context about what the parameters represent beyond the schema's technical validation.

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 tool's purpose with specific verbs ('check', 'verify') and resources ('Etherscan verification status', 'EIP-1967 proxy pattern', 'implementation/admin slots', 'dangerous admin functions'). It distinguishes from siblings by focusing on contract security analysis rather than portfolio management, staking, or transaction preparation.

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 (analyzing contract security for a given address on a supported chain) but doesn't explicitly state when to use this tool versus alternatives like 'get_protocol_risk_score' or 'check_permission_risks'. No exclusions or prerequisites are mentioned.

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