gx3_list_commands

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

No annotations are provided, so the description carries the full burden. It clearly discloses that the tool is read-only and touches no project, and it describes the output shape as a list of commands with one-line summaries. This is sufficient for a simple listing tool, though it could have been slightly richer about potential output formatting or error behavior.

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?

Three tight sentences: purpose, read-only safety, and use-before-run guidance. Every sentence earns its place, and the most important identifying information is front-loaded.

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, read-only listing tool with no output schema, the description is complete. It tells the agent what the tool does, that it is safe, what output to expect, and when to invoke it relative to gx3_run_command.

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 input schema has zero parameters, so there is no parameter behavior to document. The baseline for zero-parameter tools is 4, and the description appropriately avoids inventing parameter-like 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?

States a specific verb ('List') and resource ('every project-read-only GX3 CLI command this server will run') with a clear output promise ('one-line summary of each'). It also distinguishes itself from sibling tools by explicitly calling out that it does not run commands, separating it from gx3_run_command and the various inspection tools.

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?

Provides explicit when-to-use guidance: call this before gx3_run_command when no typed tool fits. It also explains the benefit—seeing what is actually available rather than guessing a command name—and implicitly directs users to use a specific sibling when one fits.

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