list_command

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the description adds little about side effects. It contributes the concrete HTTP mapping GET /api/v3/command, confirming the read-only behavior, but it doesn't mention response shape, pagination, or authorization, so it remains minimal rather than rich.

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 only two short lines with no filler, and the endpoint is immediately visible. It is appropriately sized for a trivial zero-parameter read tool, though the phrase 'Read Command' is somewhat terse.

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 tool with an output schema, the description is nearly sufficient, but it doesn't explicitly state that it returns the collection of commands and doesn't distinguish itself from get_command_by_id. The context signals compensate for much of the missing behavior, making it adequate but not 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?

The tool has zero parameters and the schema already documents an empty argument object, so there is nothing for the description to add. This matches the baseline for no-parameter tools.

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 names the verb 'Read' and the resource 'Command' and gives the GET endpoint, so an agent can identify it as a retrieval operation. However, it doesn't explicitly say it lists all commands or contrast it with get_command_by_id, which prevents a 5.

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?

There is no guidance on when to use this tool versus alternatives. The description simply restates the operation and endpoint, leaving the agent to infer from the tool name and sibling set that this lists commands rather than fetching a single command.

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