validate_syntax

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

Description discloses speed, lack of semantic analysis, prerequisite. No annotations provided, so description carries burden. Lacks details on error handling or side effects, but sufficient for a lightweight tool.

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?

Very concise, well-structured with usage examples, front-loaded key information. No wasted words.

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?

Covers purpose, usage, output, and distinction from sibling. No output schema, but mentions output type. Adequate for a simple validation tool.

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%. Description adds usage patterns and defaults for fileName but does not add deep parameter semantics beyond what schema provides. Baseline 3 appropriate.

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?

Description clearly states it's for quick syntax-only validation, gives usage examples, and distinguishes from sibling 'get_diagnostics' by stating it does not perform semantic analysis.

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?

Explicitly says when to use (quick syntax checks) and when not (for full diagnostics, use get_diagnostics). Also states prerequisite: load_project must be called first.

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