validate_component

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

There are no annotations, so the description carries the full burden of behavioral disclosure. 'Validate' suggests a read-only operation but does not state whether the tool returns a report, throws an error, modifies anything, or requires a selected component context. The behavior after a failed or passing validation is entirely unspecified.

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 a single short sentence with no wasted words, which is concise. However, the brevity reflects under-specification rather than efficient completeness: it lacks criteria, output, and usage context, so it is not fully earning its place as an informative definition.

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?

Given no output schema, no annotations, and a large set of overlapping sibling tools, the description is too thin to let an agent confidently select and invoke this tool. It does not state what 'design system rules' means, what result to expect, or how this differs from component_audit and similar tools.

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 100%, so the baseline is 3. The property description 'Component to validate' adds minimal meaning beyond the parameter name 'nodeId', and the tool description does not clarify what kind of node ID is expected or how to obtain it. No significant extra semantic value is added.

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 states a specific verb ('Validate') and resource ('component') and clarifies that validation is against design system rules. However, it does not distinguish itself from siblings such as component_audit, check_consistency, or lint_design, all of which could plausibly perform a similar validation.

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 given about when to use this tool versus the many related siblings (e.g., component_audit, compare_to_system, detect_inconsistencies). The description neither states when it is the right choice nor when an alternative should be used.

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