execute_tcl

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

With no annotations, the description discloses key behaviors: dangerous commands are blocked, some disabled in read-only mode, and errors are returned. It also describes the output format (dictionary with command, output, status). Could mention potential side effects or timeouts but is adequate.

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 front-loaded with the core action, followed by brief context, parameter examples, and return info. Every sentence adds value without redundancy.

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 a single parameter and an output schema, the description covers command blocking, read-only mode limitations, and error responses. It could mention execution time or concurrency but is largely complete.

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?

The sole parameter 'command' has a 0% schema description coverage, but the description provides concrete examples (WHO, DATE, LISTFILES, FILE.STAT CUSTOMERS), adding significant meaning beyond the type 'string'.

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 'Execute a TCL/ECL command and return the output,' with specific verb and resource. It explains that TCL commands are system-level, distinguishing it from query or subroutine tools among siblings.

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 explicit when-to-use or when-not-to-use guidance is given. While examples are provided, there is no comparison to sibling tools like 'execute_query' or 'call_subroutine' to help an agent choose correctly.

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