getDiagnostics

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

Annotations declare readOnlyHint=true. Description adds real-time LSP behavior when external tool connected, but does not detail fallback behavior (cached vs. stale) or coverage limitations across listed languages. Some behavioral context but incomplete.

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?

Two sentences, skillfully front-loaded: first sentence states exact purpose and languages, second adds behavioral insight. No fluff; every word earns its place.

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 exists, but description omits return format or diagnostic structure. Agents must infer what fields are returned. Lacks completeness for a data retrieval tool without schema.

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 already covers all 4 parameters with full descriptions (100% coverage). Description adds no additional meaning beyond schema fields, so baseline of 3 is 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 specifies verb 'get' and resource 'diagnostics' from multiple linters (TS, ESLint, Pyright, etc.), clearly distinguishing from siblings like 'watchDiagnostics' (streaming) and 'explainDiagnostic' (interpretation). Purpose is precise and actionable.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., watching vs. fetching, explaining vs. raw diagnostics). The name implies one-off retrieval, but description does not state usage context or exclusions, leaving ambiguity.

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