siril_list_commands

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

There are no annotations, so the description carries the behavioral burden. It discloses the list behavior and the two filtering behaviors: substring match on name/usage and scriptable-only restriction. For a simple read-only listing tool, this is adequate; it does not claim side effects or need to state auth/rate limits.

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 sentences plus a compact Args block. Every sentence earns its place: the first states the core purpose, and the Args section clarifies both parameters without filler.

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?

For a low-complexity discovery tool with an output schema available, the description covers the purpose and all parameter semantics. Sibling tools are clearly distinct by verb, so an agent should be able to select and call this tool correctly.

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 does: query is defined as an optional substring filter on command name or usage, and scriptable_only is defined as limiting results to scriptable commands. Both parameters get meaningful semantics beyond their raw schema titles and defaults.

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 a specific verb and resource: 'List Siril commands available for scripting.' This clearly distinguishes it from sibling tools like siril_run_command and siril_run_script, which execute commands rather than enumerate them.

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 phrase 'available for scripting' and the query/filter arguments imply this is a discovery tool to find commands before scripting, but the description never explicitly says when to prefer it over siblings or when not to use it. Usage context is implied, not stated.

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