td_execute

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

No annotations are provided, so the description carries full burden. It mentions 'execution in TD's main thread' but omits other behavioral traits like whether it is synchronous, error behavior, or permission requirements. This is insufficient for a code execution tool.

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 short (two sentences) and front-loaded with the main action. However, it lacks structure or additional sections (e.g., return value description) that would be helpful for such a tool. It is concise but not optimally structured for completeness.

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 no output schema and no annotations, the description should compensate with details about behavior (e.g., error handling, blocking nature, side effects). It does not, leaving the agent underinformed for safe and effective use.

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?

With 0% schema description coverage, the description adds value by explaining the 'code' parameter as 'Python code to execute in TD's main thread' and 'return_expression' as 'Optional expression to evaluate and return'. This clarifies the purpose beyond the schema's type-only definition, but it does not detail expected formats or constraints.

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 Python code inside TouchDesigner', which is a specific verb and resource. It distinguishes this tool from siblings like td_delete_op or td_get_root, all of which have different purposes. The purpose is 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 provides no guidance on when to use this tool vs alternatives, prerequisites, or context. For a code execution tool, it's critical to mention safety or error handling, but none is given.

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