run_custom

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Run a custom PowerShell tool' without mentioning potential side effects, permissions, or output behavior. For a tool that executes arbitrary scripts, this is a significant gap.

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?

Two sentences: the first states the purpose, the second provides a necessary pointer to list_custom_tools. Every sentence earns its place with no redundancy or filler.

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?

With no output schema or annotations, the description is minimal. It references the config file and list_custom_tools, but omits important behavioral details about script execution and system effects. For an arbitrary script runner with potentially broad impact, this is insufficient.

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 input schema covers both parameters (tool_name and params) with clear descriptions, achieving 100% coverage. The description adds that the tool must be registered in a-eyes.config.json, which provides context for tool_name, but does not elaborate further beyond the schema.

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 action ('Run a custom PowerShell tool') and the resource ('registered in a-eyes.config.json'). It distinguishes from siblings by referencing list_custom_tools for discovery, making the tool's purpose specific and unambiguous.

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 instructs to use list_custom_tools to see available tools, which is a useful prerequisite for choosing the correct tool_name. However, it does not explicitly contrast with alternative tools or state when not to use this tool, leaving usage guidance implied rather than explicit.

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