Angular: template errors

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

With no annotations, the description carries the burden of behavioral disclosure. It adds valuable caveats about the empty list meaning 'no errors' only when the server is healthy and hints at output structure via 'entry anchored in the companion file'. However, it does not explain side effects, required permissions, or error conditions beyond server health.

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 short but poorly written. Phrases like 'files checks a batch' are ungrammatical, and 'An entry anchored in the companion file names it in file' is cryptic and adds confusion rather than clarity. The useful 'server healthy' caveat is buried in an unclear sentence.

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 and no annotations, the description is insufficient to fully understand the tool's behavior. It lacks details on the response format, error listing structure, or what happens when both 'file' and 'files' are omitted. The tool is a diagnostic tool with moderate complexity, but the description does not adequately cover it.

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 description supplements the schema by stating accepted file extensions (.html or .ts) and that 'files' handles batch checks. Since schema coverage is 100%, this extra context is helpful but not extensive; it does not clarify parameter precedence or batch limits.

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 opening phrase 'Angular compiler errors for a template after an edit' clearly indicates the tool reports compiler diagnostics for templates. This differentiates it from sibling tools like ng_component_info or ng_find_usages, though the rest of the description is grammatically confusing.

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 explicit guidance on when to use this tool versus alternatives is provided. The phrase 'after an edit' implies a context, but there is no mention of when not to use it or how it compares to sibling tools.

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