execute_claude_script

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

Description discloses several behavioral aspects: auto-detection, installation, package management, logging, script length monitoring, and report generation. However, it does not address potential destructive effects of script execution.

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 uses bullet points and emojis which are clear but somewhat verbose. Could be more succinct.

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 tool lacks an output schema, and the description does not explain what the tool returns to the agent (e.g., execution result, path to report). Missing this information for agent decision-making.

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 already provides descriptions for all three parameters. The tool description does not add further parameter semantics beyond what is in 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?

Description clearly states the tool detects and executes Python scripts for bioinformatics tasks, distinguishing it from sibling tools that analyze tasks or debug workflows.

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?

Despite listing features, the description does not provide explicit guidance on when to use this tool versus siblings. Usage context is implied but not stated.

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