trmm_list_scripts

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds useful context that the tool returns script ids needed by trmm_run_script, but does not disclose other behavior like pagination, output shape beyond ids, or how search/limit affect results.

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 sentences with no wasted words. The primary purpose is stated first, followed by the most important output detail. It is appropriately sized for a simple list tool.

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 description covers the core purpose and the key output needed for trmm_run_script, but there is no output schema and no explanation of limit/search semantics or whether additional script fields are returned. For a simple optional-parameter list tool this is acceptable but not fully 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?

Schema description coverage is 0%, and the description does not mention the 'limit' or 'search' parameters at all. Although the parameter names are relatively self-explanatory and optional, the description provides no added meaning to help an agent understand how search filtering or result limiting behaves.

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 a specific action and resource: listing scripts available in TRMM. It also explains the key output value — each script's id — and connects it to the downstream trmm_run_script tool, which differentiates it from sibling list tools like trmm_list_agents and trmm_list_alerts.

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 gives clear context for when this tool is useful: when you need the script id required by trmm_run_script. It does not explicitly contrast this with alternative tools or specify when not to use it, but the purpose is clear enough to guide selection.

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