check_setup

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

readOnlyHint=true already signals a safe read, and the description adds genuine behavioral context beyond that: it is a diagnostic that reports absence vs presence, scopes itself to the checks' toolchain, and promises 'exact fixes for anything missing.' It does not contradict the annotation.

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?

One dense sentence that front-loads the core action and appends the conditional repo_path behavior. Efficient with no filler, though the enumeration of toolchains makes it slightly heavy to parse on first read.

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 no output schema, the description does the right amount of work: it names the scope of diagnosis and the shape of the result ('exact fixes for anything missing'). An agent knows what it will get and when the repo_path variant applies.

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?

The single optional parameter is fully documented in the schema, and the description goes further by explaining what repo_path actually changes: which interpreter the repo's checks would resolve and whether its test deps are installed. That adds decision-relevant meaning beyond the schema string.

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 ('Diagnose') and resource ('the local setup'), then enumerates exactly what is inspected: git, Python, node/npm, go, poetry, conda, plus repo-specific interpreter and test-dependency status. This is clearly separable from siblings like find_repos or run_relevant_checks.

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 intent (pre-flight environment diagnosis) is implied by 'the checks use' and the repo_path behavior, but the description never says when to call this versus run_relevant_checks or start_task, nor does it state any when-not conditions. Usage must be inferred.

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