List Available Archicad Commands

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds some output scope detail ('comprehensive list', 'brief descriptions') but does not disclose additional behavioral traits such as payload size, pagination, or response structure. It provides useful workflow context but not deeper behavioral transparency.

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 compact, front-loaded with the core purpose, and uses a clear STEP 1/STEP 2 structure. Every sentence earns its place, and the most important instruction—use this first—is prominent.

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 zero-parameter discovery tool with an output schema and rich annotations, the description is complete. It tells the agent exactly what the tool returns, when to use it first, and which sibling tool to proceed with. Nothing needed to call it correctly is missing.

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 tool has zero parameters, so the baseline is 4 and the description need not explain argument semantics. The empty input schema already makes clear that no arguments are required, and the description focuses on the tool's role rather than introducing unnecessary parameter details.

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 the tool returns a comprehensive list of all available Archicad API commands and brief descriptions, using a specific verb and resource. It also differentiates itself from sibling tools by explicitly positioning itself as the discovery step before calling archicad_get_command_schema.

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 explicit step-by-step guidance: use this tool FIRST to find the correct command name, do not guess or hallucinate names, and then use archicad_get_command_schema to learn exact arguments. This clearly states when to use this tool and what to do next.

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