Validate component integration

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: it returns structured findings plus fixes, and explicitly does not execute callbacks — a meaningful side-effect boundary the annotations do not convey.

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?

Two tight sentences with no filler; the validated surface is front-loaded and the behavioral caveat follows. Efficient and well-ordered for its size.

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?

An output schema exists, so return value detail is not owed by the description, and the read-only nature is covered by annotations. However, the low parameter coverage and absence of any when-to-use/alternative routing leave gaps for an agent deciding whether to call this versus validate_markup.

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 description coverage is only 13% across 8 parameters, so the description must compensate. It narratively covers markup, stylesheets, SVG symbols, ID references (externalIds), initialization, and handledEvents, but omits controllers and componentIds and gives no format/syntax detail. Partial compensation justifies a mid score.

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 (check) and enumerates exactly what is validated: markup, stylesheet dependencies, SVG symbols, ID references, initialization, and declared events. This is far more concrete than the title, though it never explicitly distinguishes itself from the sibling validate_markup beyond the implicit 'integration' scope.

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 when-to-use guidance and no mention of the obvious sibling validate_markup, which an agent would need to choose between. The scope (integration-level) is only inferable from the name and the checklist of what it inspects.

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