vaultpilot-mcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the tool's function but omits critical details like whether it's read-only or mutative, potential rate limits, authentication requirements, or error handling for invalid inputs. This is a significant gap for a tool analyzing contract permissions.

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, dense sentence that efficiently conveys the tool's core functionality without unnecessary words. It is front-loaded with the main action and resource, making it easy to parse quickly.

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 complexity of analyzing contract permissions and the lack of annotations and output schema, the description is insufficient. It doesn't explain the return format (e.g., structured risk classifications), error cases, or dependencies on contract standards, leaving gaps for an AI agent to use the tool 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?

The description does not explicitly mention the parameters, but it implies their use by referring to 'a contract' (matching the 'address' parameter) and context like 'Ownable.owner' (hinting at blockchain context via 'chain'). With 0% schema description coverage, this implicit context adds meaningful value beyond the bare schema, though it doesn't detail parameter formats or constraints.

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 ('Enumerate', 'classify') and resources ('privileged roles on a contract', 'holders'), and distinguishes it from siblings by focusing on permission risk analysis rather than general security checks, 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 provides no guidance on when to use this tool versus alternatives like 'check_contract_security' or other sibling tools. It lacks context about prerequisites, such as needing a contract address with specific interfaces, or exclusions for non-contract addresses.

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