Get TD Python class details

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

The description adds that it returns 'full documentation' including members and methods, which goes beyond the readOnlyHint annotation. However, it does not disclose potential limitations like dependency on a knowledge base or error handling for unknown class names.

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, efficient sentence with no unnecessary words. It conveys the essential information without fluff, making it 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?

For a simple single-parameter tool with annotations indicating safety, the description adequately covers what the tool does and returns. It could be more specific about the return format, but given the absence of an output schema, it is 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?

The input schema fully describes the class_name parameter with examples. The description adds no additional parameter context, but the existing schema coverage is sufficient, so a baseline score of 3 is appropriate.

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's purpose: providing full documentation for one TouchDesigner Python class, including members and methods. It differentiates from siblings like get_td_classes (which lists classes) and get_module_help (for modules).

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 implies its use case: retrieve detailed info for a specific class. It does not explicitly mention when not to use or alternatives, but the context of sibling tools provides sufficient guidance.

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