td_read_chop

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only hints at glob pattern support for channels, but says nothing about whether the CHOP is evaluated/cooked, whether values are real-time, or any side effects. This is insufficient for a read operation on a node-based system.

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 very short with no redundant words, but it is so terse that it lacks a subject-verb structure, making it more a label than an instruction. It is not as concise-with-meaning as it should be.

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 an output schema, the minimum needed from the description is context on when to use this tool and what the path refers to. Neither is provided. The description is too sparse for an agent to confidently select this tool over siblings.

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 0%, so the description must compensate. It adds the 'glob filter' note, which applies to the channels parameter, but it does not explain the crucial 'path' parameter or how patterns interact with channel names. This leaves most parameter meaning undefined.

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 'Current channel values of a CHOP (glob filter)' identifies the resource (a CHOP) and suggests a read operation, but uses a noun phrase instead of an explicit verb like 'read' or 'get'. It distinguishes from td_find_channels by focusing on values rather than names, but is vague about what 'current' means in an execution context.

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 usage guidance is provided. The description does not state when to use this tool instead of siblings like td_get, td_list, or td_find_channels, nor does it mention any prerequisites or context.

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