eslint_generate_config

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

With no annotations, the description carries the full burden, but it only says config generation occurs. It does not disclose whether a file is written or overwritten, what the generated output looks like, or how the optional api_key affects 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?

The description is one short sentence with no filler, and the main action is stated first. However, it is so terse that some of that brevity comes at the expense of useful detail.

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 configuration-generation tool with no annotations and no output schema, this is incomplete: it omits the expected output artifact, overwrite behavior, and differentiation from sibling ESLint tools. The two parameters are documented in the schema, ut the operational context around them 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 input schema already describes both parameters at 100% coverage, so the description adds no additional semantics. The 'with rules' phrase loosely relates to generation behavior but does not clarify api_key usage or the meaning of directory beyond the schema.

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 concrete verb and resource ('Generate ESLint configuration with rules'), so an agent can understand the core action. It does not differentiate from sibling tools like eslint_add_plugins or eslint_fix_violations, though the distinction is mostly inferable from tool names.

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?

No guidance is provided about when to choose this tool over eslint_add_plugins or eslint_fix_violations, nor about prerequisites such as an existing project directory or when the Pro/Enterprise api_key is needed. The usage context is only implied by the tool name and schema.

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