generate_class

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the agent knows this is a writing, non-idempotent operation. The description adds the directory-placement constraint but never says whether an existing class file of the same name is overwritten — the single most important behavioral fact for a destructive generator.

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?

Purpose is front-loaded in one clean sentence, which is good. But the follow-up is garbled ('Either run this command existing directory of this name'), wasting space on awkward and partly unparseable instructions.

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 destructive, open-world generator with no output schema and effectively undocumented nested parameters, the description omits overwrite semantics, success/failure reporting, and reliable parameter naming. What an agent needs in order to call this safely is not covered.

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 coverage is reported at 0% for a nested input object, so the description must compensate. Instead it introduces a CLI-style '--output-dir' flag name that does not match the schema's 'outputDir', and says nothing about the 40-character/letter-start rule for the required name.

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+resource: generates the Apex *.cls file plus its metadata file. That distinguishes it from generate_component and generate_trigger by artifact type, though the description never names those siblings to route the agent explicitly.

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 only guidance is about file placement (files 'must' live in a parent 'classes' directory, or use the flag to create/point to one). There is no when-to-use statement, no prerequisites, and no comparison against alternative generators.

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