Check config files against their schemas

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context the annotations don't: what each reported error contains (line, path, allowed values, suggested key) and that it also emits misspelling/deprecation warnings.

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?

Front-loaded with the core action, followed by one supporting sentence on error detail; the parenthetical file-kind list is dense but earns its place as scope evidence. No filler sentences.

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?

With an output schema present, return values need not be described, and annotations carry the safety profile. The main omission is batch constraints (maxItems 20, per-file size limits) that an agent calling with many files would benefit from knowing.

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 only 50% (the 'content' property is undocumented). The description partially compensates by explaining that the file path/name drives schema and format selection, but it never mentions the 'schema' override parameter that applies one schema to every file, leaving that behavior to the schema alone.

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?

States a specific verb+resource ('Checks config files against their official JSON Schema from SchemaStore') plus the mechanism (schema chosen by file name) and supported formats. This is clearly distinguishable from config_help and find_schema, which cannot validate file contents.

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?

Usage is strongly implied by the purpose (validate a config file's content), and naming the supported file kinds hints at scope. However, there is no explicit when-to-use/when-not guidance and no routing to the sibling tools (e.g., use find_schema to obtain a schema, config_help for guidance).

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