sf_generate_lwc_component

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

The description does not disclose side effects, such as file overwriting, deployment to org, or the meaning of 'baseline'. Since no annotations are present, the description carries the full burden, and it fails to mention important behavioral factors like the overwrite/confirm/deployAfterGenerate parameters.

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 sentence that is efficient and front-loaded with the action verb, containing no filler words. It earns its place as a concise summary.

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 tool with 12 parameters and no annotations or output schema, this one-sentence description is grossly insufficient. It lacks information about return values, prerequisites, conflict handling, and deployment behavior.

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?

With 0% schema description coverage and no parameter explanations in the description, the semantics of 12 parameters (e.g., overwrite, exposeTargets, ignoreConflicts) are entirely unclear. The description only mentions 'baseline' without elaborating.

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 clearly states the tool's function: generating baseline LWC component files within a Salesforce project. It uses a specific verb ('Generate') and resource ('LWC component files'), distinguishing it from the many query/execute/deploy sibling 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?

There is no guidance on when to use this tool vs alternatives, or under what conditions (e.g., replacing existing components, handling conflicts). No prerequisites or exclusions are mentioned.

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