list_api_commands

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

With no annotations provided, the description carries the behavioral burden. 'Catalog of ALL available commands' and the verb 'list' clearly imply a read-only, non-mutating operation. It also adds useful scope context (official JSON API + Tapir) and the optional group filter behavior, though it does not discuss output volume or ordering.

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, compact sentence and front-loads the core purpose. Every word adds value, and there is no redundant metadata or 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?

The tool is simple, with one optional parameter and an output schema present, so the description does not need to explain return values. The description covers what the tool does, what it includes, and how it can be narrowed, which is sufficient for safe selection. It could mention how groups are structured, but the overall context is reasonably 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 coverage is 0%, so the description must clarify the parameter. It states that 'group' filters the catalog, which adds meaning beyond the schema's raw field name. However, it does not explain what group values are valid, how to discover them, or the exact format/usage of the filter.

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 pattern ('Catalog...') with a clear resource: ALL available Archicad API commands across both official JSON API and Tapir. It also distinguishes itself from sibling tools like describe_api_command and execute_api_command by being a catalog/list operation.

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 the tool is meant for discovering/browsing available commands, and the optional group filter gives a sense of when it might be narrowed. However, it does not explicitly state when to use this tool versus describe_api_command or execute_api_command, nor does it mention any exclusions.

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