syntaxCheckTypes

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'Diagnostic'. It adds useful scope detail by framing the flavours from the check endpoint's perspective, though it does not describe the exact return shape. For a zero-parameter read-only listing, that is a minor omission.

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?

Both sentences are short and each adds distinct information: what the tool lists and how syntaxCheckCode relates to it. The first sentence is a fragment rather than a direct verb phrase like 'Lists...', which costs a point but does not waste 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?

For a zero-input, annotated read-only diagnostic tool, the description covers purpose and sibling relationship well. It does not mention the output representation, but the natural reading is an enumeration of flavour names, and there is no output schema to fill that gap.

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?

There are no parameters, so the 0-param baseline of 4 applies. The description appropriately says nothing about inputs, and no schema coverage gap needs compensating.

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 identifies a specific resource ('syntax-check flavours') and scope ('this system', 'as the check endpoint understands them'), and distinguishes itself from syntaxCheckCode, which selects the flavour automatically. Though the verb is implied ('which...offers'), the intent to enumerate available values is unambiguous.

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?

It explicitly labels the tool as 'Diagnostic' and says syntaxCheckCode picks the right flavour itself, which tells the agent this is a discovery/helper tool rather than something needed for normal syntax checking. This gives a clear when/when-not cue relative to a sibling.

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