td_python_help

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, which communicate safe, non-destructive behavior. The description adds no additional behavioral context, such as whether it evaluates Python code or how errors are handled. With annotations present, the description meets the minimum but does not add extra value.

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, clear sentence with no unnecessary words. It is front-loaded and efficiently conveys the tool's purpose.

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 tool's simplicity (one parameter, output schema present, low complexity), the description is adequate. It could briefly mention the return format (e.g., string of documentation), but the output schema likely covers that. Overall, it is reasonably complete for the tool's scope.

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 description coverage is 100%, and the parameter description for 'target' is already explicit. The tool description does not add any meaning beyond what the schema provides, so it meets the baseline without compensating.

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 retrieves Python help documentation for TD classes/modules. It is specific about the resource ('Python help documentation') and the target ('TD class/module'), but could be more precise about whether it returns docstrings or interactive help. It distinguishes from siblings like 'td_python_classes' and 'td_get_param_help', but not explicitly.

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 versus alternatives such as 'td_search_official_docs' or 'td_python_classes'. There is no mention of prerequisites, suitable contexts, or situations where this tool should be avoided.

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