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

No annotations provided, so description carries full burden. 'Lint' suggests read-only checking, but does not explicitly state whether it modifies anything, what side effects occur, or whether it requires network access. Behavioral traits are underspecified.

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?

Single sentence, no unnecessary words. Information is front-loaded and efficiently delivered.

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?

No output schema and no description of return values. For a linter, the output format (e.g., list of errors/warnings) is crucial but omitted. Incomplete for a tool with single parameter and no sibling differentiation beyond purpose.

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 0% and only one parameter 'text' (string). Description only mentions 'tsconfig.json structure' and 'compilerOptions, strict hints', but does not clarify that 'text' should be the raw JSON content. Adds minimal meaning beyond the schema.

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?

Clearly states the tool lints tsconfig.json structure, specifically compilerOptions and strict hints. Verb 'lint' and resource 'tsconfig.json' are specific. Among sibling lint tools, it uniquely targets TypeScript config.

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?

Implies usage when you need to check a tsconfig.json, but does not provide explicit when-to-use or when-not-to-use guidance, nor alternatives. Lacks context for exclusion or comparison with other lint tools.

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