provider_subcommands_list

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

Annotations already cover readOnlyHint, idempotentHint, and destructiveHint. The description adds useful behavioral context: the result is compact, filterable, based on declared subcommands, and deliberately excludes flags and raw help. No contradiction with annotations, and the behavior beyond the schema is described clearly.

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?

A single, densely informative sentence with no filler. It front-loads the action and resource, then adds the key constraints ('compact', 'filterable', 'without flags or raw help'). Every word earns its place.

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 read-only, fully optional-parameter list tool, the description is nearly complete: it states the subject, the filtering capability, and what is deliberately excluded. There is no output schema, so a note on the exact item shape would add value, but the simplicity of the tool and strong annotations make this a minor gap.

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%, and every parameter already has a clear description with enums where applicable. The description's word 'filterable' reinforces the parameter model but adds no parameter-specific detail beyond what the schema provides, so baseline 3 is appropriate.

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 a specific verb ('Return'), a resource ('catalog of declared provider CLI subcommands'), and explicit exclusions ('without flags or raw help'). This makes the tool's purpose unambiguous and clearly distinguishes it from raw help and deeper provider subcommand 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?

The read-only, catalog-oriented wording implies use for quick overviews or filtered listings rather than deep contract inspection. However, it does not explicitly name alternatives like provider_subcommand_contract or provider_subcommand_drift, nor state when those would be more appropriate.

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