generate_component

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

Annotations already declare destructiveHint=true, readOnlyHint=false, openWorldHint=true, and idempotentHint=false, so the safety profile is covered. However, the description adds nothing beyond that: it does not say whether existing files are overwritten, what files are created, or that it writes to the local filesystem — important for a destructive, non-idempotent 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?

A single efficient sentence with no filler, front-loading the verb and resource. It is appropriately sized, though it is perhaps too terse for the scope of what the tool does.

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, non-idempotent file-generating tool with no output schema, the description omits overwrite behavior, what artifacts are produced, and any prerequisites. Annotations cover the safety flags but leave these operational questions unanswered.

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 nested schema actually documents all four sub-parameters in detail (name length limits, type values aura/lwc, template values, outputDirectory semantics), despite the reported 0% coverage metric. The description adds no parameter-level meaning, so the schema carries the burden and baseline 3 applies.

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 (Generate) and resource (Lightning Web Components / Aura components) with scope modifiers (templates, output directories). It is distinguishable from siblings like generate_class and generate_trigger, though the shared 'generate_*' family pattern is not explicitly contrasted.

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 on when to choose this over generate_class, generate_trigger, or schema_generate_tab, and no prerequisites (e.g., whether a default org or login is required) are stated. The agent must infer usage entirely from the name.

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