cli_add_commands

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

With no annotations provided, the description carries the full behavioral disclosure burden. It only restates the action ('add') without explaining side effects, whether existing commands are preserved, whether an API key is needed, or what happens on validation failure. The promise of 'validation' is not backed by any schema or annotation detail.

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 front-loaded sentence with no filler. It loses one point because 'arguments' and 'validation' are unsupported by the schema, making the sentence slightly less precise than it appears.

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 has no annotations and no output schema, so the description must supply operational context. It does not explain what 'existing CLI' means in terms of cli_name, whether the operation is idempotent, what the return value is, or how existing commands are affected. The schema covers parameter names but not the behavioral context an agent needs.

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 100%, so the baseline is 3. The description adds little beyond the schema and even introduces 'arguments' and 'validation' terms that do not map to schema properties; it does not clarify the meaning of api_key or the expected format of command options.

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 action (add subcommands) and target (an existing CLI), which distinguishes it from CLI scaffolding tools. However, it mentions 'arguments' and 'validation' that have no corresponding fields in the input schema, creating slight ambiguity about what the tool actually supports.

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 'to an existing CLI' implies this tool is for extending an already-created CLI rather than generating a new one. However, no alternatives are named and no explicit when-to-use or when-not-to-use guidance is provided among the many sibling CLI-related tools.

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