Validate UI5 view/fragment

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

No annotations are provided, so the description carries the burden. It discloses what the tool checks (XML well-formedness and event handler existence in controller) and that it returns failures. However, it doesn't describe side effects (read-only nature), what happens on malformed paths, or failure behavior detail. For a validation/read tool this is moderate transparency.

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, front-loaded sentence that states purpose, scope, and output value. It is efficient with no filler. Could arguably add sibling differentiation but is appropriately compact.

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 the complexity (validation tool, 2 params, no output schema, no annotations), the description covers the core purpose and output but omits: whether controllerPath is truly optional, the exact return structure, and how it relates to ui5_lint. For a tool meant to drive an agent fix loop, slightly more detail on output format would help.

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 both parameters (xmlPath, controllerPath) are documented. The description clarifies that xmlPath must be a .view.xml or .fragment.xml and that controllerPath must implement the handlers, which adds context beyond raw schema text. But it doesn't mention that controllerPath appears optional (not in required list), leaving ambiguity.

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('validates') plus the resource ('UI5 view/fragment'), and clarifies the scope: checks XML well-formedness and all declared event handlers exist in the controller. It doesn't explicitly differentiate from siblings like ui5_lint, but the 'validation loop' terminology and event-handler focus distinguish it somewhat.

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 description implies 'run this to validate UI5 views and get failures to fix,' and notes it returns failures for the agent to fix. However, it doesn't explicitly state when to use this vs ui5_lint or cap_validate, nor any exclusions. The guidance is implied rather than explicit.

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