tdarr_debug_vars

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

No annotations are present, so the description must fully convey behavioral traits. It only states it retrieves debug info, without disclosing side effects, permissions, rate limits, or output format. The tool likely performs a read operation, but this is not confirmed.

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 extremely concise (5 words) but lacks structure and fails to provide essential details. It is a fragment rather than a complete sentence, which hurts readability and informativeness.

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 single parameter with undocumented values, no output schema, and no behavioral disclosure, the description is insufficient for an agent to correctly invoke this tool. It does not explain what 'type' values are acceptable or what kind of debug info is returned.

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% for the single parameter 'type,' which has a basic description. The description adds no additional meaning beyond 'by type'; it does not list valid values, format, or examples. Baseline 3 applies since schema covers the parameter but description adds no value.

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 states it 'get various debug info by type,' which identifies the tool's general purpose but lacks specificity about what debug info is included or how 'type' is used. It does not differentiate from sibling debug tools like 'tdarr_get_process_info' or 'tdarr_get_time_now'.

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?

No guidance is provided on when to use this tool versus alternatives, such as other debug-related tools. There is no mention of prerequisites, exclusions, or recommended contexts.

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