get_diagnostics

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds useful context about the specific linting tools used (Verilator, verible-verilog-lint, GHDL) and mentions they are part of OSS CAD Suite, which helps understand implementation details. However, it doesn't disclose rate limits, error handling, or performance characteristics that would be valuable for an agent.

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?

The description is efficiently structured in two sentences: the first states the core purpose and output format, the second specifies the tools used per language. Every sentence adds value with no wasted words, making it appropriately sized and front-loaded with essential information.

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?

Given no annotations and no output schema, the description provides good purpose and tool implementation context but lacks details about return values, error conditions, or operational constraints. For a diagnostic tool with 2 parameters, it's adequate but has clear gaps in behavioral completeness that would help an agent use it effectively.

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 100%, so the schema already fully documents both parameters. The description doesn't add any parameter-specific information beyond what's in the schema (e.g., it doesn't explain code format expectations or language variant implications). Baseline 3 is appropriate when the schema does all the parameter documentation work.

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 clearly states the tool's purpose with specific verbs ('return structured lint diagnostics') and resources ('HDL source'), including details about the diagnostic format (line, column, severity, message) and the specific tools used for different languages (Verilator, verible-verilog-lint, GHDL). It distinguishes from siblings like 'lint_hdl' by specifying the structured diagnostic output format.

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?

The description implies usage for HDL source code linting with specific language variants, but does not explicitly state when to use this tool versus alternatives like 'lint_hdl' or other siblings. It provides context about the tools used but lacks explicit guidance on when/when-not to use it or named alternatives.

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