execute_typescript

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

With no annotations, the description fully discloses behavior: sandboxed Node.js environment, temp file deletion, optional network allowlist, timeout, memory, and CPU limits, and best-effort security. This is comprehensive.

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 informative and well-structured, with bulleted args and highlighted important points. Some verbosity with uppercase IMPORTANT, but still efficient and easy to parse.

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 there is an output schema, the description does not need to explain return values. It covers both parameters, provides crucial context about token savings and security, and is complete for the tool's complexity.

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 adds meaning beyond the input schema: 'code' is explained as TypeScript code with import capability, and 'timeout' is described as max execution time in seconds with default. Schema coverage is 0%, so description fully compensates.

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 'Execute TypeScript code in a Node.js environment with access to Canvas API,' specifying the verb, resource, and environment. It also mentions the ability to import from './canvas/*' modules, distinguishing it from sibling tools that are primarily Canvas CRUD operations.

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 explicit guidance on when to use (99.7% token savings for bulk operations) and important security considerations. While it doesn't explicitly state when not to use or compare with alternatives, the context is clear.

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