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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false), the description discloses the underlying commands executed and the normalized return payload (console_logs, passed/failed/total, stdout, stderr, duration). It does not warn that running a script may exercise external systems reachable via base_url, which matters given openWorldHint=true.

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?

Three tight sentences: what it runs, what it returns, then the disambiguation from run_tests. No filler, and the routing cue sits at the end where it is easy to scan.

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, the description carries the return-value burden and does so by enumerating the normalized result fields. It is nearly complete for an execution tool, missing only a note that script execution can hit live endpoints and that failures surface as results rather than tool errors.

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 the schema already documents all three parameters including the context and base_url constraints; the description's notes that framework is derived from the script record largely restate the schema. It adds a marginal detail by naming the accepted framework values, but nothing on how base_url affects execution.

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?

States a specific verb (run) plus the exact resources (Rust cargo test / Go go test automation scripts) and the shape of what comes back. It explicitly names run_tests as the sibling for Playwright/pytest, so an agent can disambiguate without opening either schema.

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?

Gives an explicit selection rule ('compiled-language script, framework rust_cargo or go_test, native runner path') and an explicit exclusion with the alternative to use instead ('For Playwright / pytest scripts, use run_tests'). Both the when and the when-not are present.

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