Execute custom tools defined in project configuration by passing tool names and arguments to replace placeholders, enabling AI agents to interact with VS Code.
Execute a custom tool defined in project configuration
| Name | Required | Description | Default |
|---|---|---|---|
| toolName | Yes | Name of the custom tool to run | |
| args | No | Arguments to pass to the custom tool (replaces {{key}} placeholders) |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description only says 'Execute' with no disclosure of behavioral traits such as side effects, permissions, or error handling. This leaves the agent with insufficient behavioral context.
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 concise sentence that front-loads the core purpose without any wasted words.
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?
The description only states purpose but lacks details on prerequisites, return values, or execution context. Given the tool runs arbitrary custom code, more context is needed for safe invocation.
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 coverage is 100%, so baseline is 3. The description does not add meaning beyond the parameter descriptions already in the schema, which adequately document toolName and args.
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 executes a custom tool defined in project configuration, using a specific verb 'Execute' and resource 'custom tool defined in project configuration', distinguishing it from sibling tools like run_command or run_javascript.
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 when a custom tool is configured, but provides no explicit guidance on when to use alternatives or when not to use this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.