cmw_wlan_trigger_catalog

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

With no annotations, the description carries the burden of disclosing behavior. The verb 'List' inherently signals a read-only operation, and 'this instrument supports' implies a query to the device. However, it does not explicitly state that no state is modified, nor does it mention any connection requirements or error conditions.

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 redundant words. It is appropriately front-loaded with the action and resource, making it easy to parse quickly.

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 is a simple list operation, and the description conveys the core purpose. However, without an output schema, it does not specify the format of the returned list (e.g., names, codes, or options). Additionally, the two undocumented parameters create a gap, so the description is not fully complete for smooth invocation.

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 only 33% (only 'meas_instance' has a description). The tool description does not mention any of the parameters, leaving 'host' and 'port' completely undocumented. It fails to compensate for the low schema coverage, so the agent gains no additional parameter semantics from the description.

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 uses a specific verb 'List' and identifies the resource 'WLAN trigger sources' with scope 'this instrument supports'. It clearly distinguishes itself from sibling tools like 'cmw_wlan_trigger' and 'cmw_wlan_set_trigger' by focusing on discovering supported sources rather than triggering or configuring.

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 a discovery role: to see which trigger sources are available before setting a trigger. However, it provides no explicit context about when to use it vs alternatives, nor does it mention any prerequisites such as needing a connection to the instrument.

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