Get TouchDesigner tutorial

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

The description opens with 'Read-only', aligning with annotations (readOnlyHint=true, destructiveHint=false). It adds context about the multiple operation modes beyond the annotation hints, though no additional behavioral traits like rate limits or auth are mentioned.

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 a single sentence that front-loads the important 'Read-only' qualifier and clearly enumerates three distinct operations. No extraneous words.

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 the presence of a full output schema and complete parameter descriptions, the description adequately covers the tool's functionality. It could be slightly more explicit about default behavior when no parameters are provided, but it's sufficient.

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% with parameter descriptions. The description summarizes the parameter usage (list, search, retrieve, include content) but does not add new semantics beyond the schema; it reaffirms the documented behavior.

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 tool lists, searches, and retrieves TouchDesigner tutorials, using specific verbs and resource (tutorials). It distinguishes itself from siblings like search_operators or get_td_nodes by explicitly targeting tutorials.

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 explains the three modes (list, search, retrieve by id/name) and the optional full content. It implies usage for tutorial-specific operations, though it does not explicitly contrast with sibling tools or state when not to use it.

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