Angular: declaration of a template symbol

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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds useful context about 0-based line/character coordinates and support for .html or inline .ts templates, but it does not disclose what happens when no declaration is found, the return format, or any error behavior. This is a moderate gap for a tool with no annotations.

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 with no wasted words. It efficiently communicates the core transformation and coordinate convention without extraneous information.

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?

The tool is relatively simple, but the absence of an output schema means the description should explain what the caller receives (e.g., declaration location, range, or null). It also doesn't mention edge cases like invalid positions or unresolved symbols. Given these gaps and the existence of sibling tools, the description is not fully complete, though it covers the essential purpose and input semantics.

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 low (33% — only 'file' has a description). The description compensates by clarifying the 0-based LSP-compatible semantics of line and character, and by specifying valid file types (.html or .ts with inline template). This adds meaningful value beyond the schema, though the description doesn't detail file path formats.

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: mapping a position in Angular template files (.html or inline .ts) to its TypeScript declaration. This specific verb-resource pairing distinguishes it from sibling tools like ng_find_usages (usages) and ng_template_diagnostics (diagnostics).

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 usage through the title 'declaration of a template symbol' and by describing the input position, but it does not explicitly state when to choose this tool over alternatives, nor does it mention any exclusions or prerequisites. Usage guidance is understood but not stated.

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