td_logger_status

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds valuable context: it inspects Python's logging module (not TD's), requires 'full' exec mode, and lists what is inspected (log level, handlers, registered loggers). No contradictions.

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 two short, clear sentences. It front-loads the purpose and adds critical notes in a compact format. No wasted 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?

The tool has no parameters but an output schema exists. The description explains what is inspected and the key distinction from TD native logging, plus the exec mode requirement. This is complete for a read-only inspection tool.

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?

There are zero parameters and schema description coverage is 100% trivially. With no parameters, the description does not need to add parameter information. Baseline 4 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 inspects Python logging configuration (log level, handlers, registered loggers) in TouchDesigner, and explicitly distinguishes it from TD's native logging. This is a specific verb+resource that differentiates it from siblings like td_python_env_status.

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 notes it requires 'full' exec mode, providing a usage prerequisite. It also clarifies it inspects Python logging, not TD native logging, which implicitly guides against using it for native logging. However, it does not explicitly name alternative tools or give when-not-to-use scenarios.

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