Biome Check

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds a performance claim ('Rust-based, roughly 25× faster than ESLint') which is not behavioral but gives context. It does not describe side effects or output, but those are not required given the low-risk nature and existing annotations.

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 a single, efficient sentence with no filler. It front-loads the core purpose and adds a relevant performance note. While it omits usage guidance, that is a separate dimension; as a concise statement of intent, it is well-structured.

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 the tool's simplicity (one parameter, no output schema) and annotations that cover read-only/idempotent behavior, the description is adequate but minimal. It lacks any mention of when to use it or how it relates to sibling check tools, which leaves an agent with incomplete context for tool selection.

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 schema fully documents the only parameter 'path' as 'Absolute path to the repository root' (100% coverage). The description adds no additional parameter semantics, so it meets the baseline but does not enhance understanding 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?

The description clearly states the tool performs 'Biome lint and format check', specifying a concrete verb ('check') and resource (Biome). It also adds a performance comparison to ESLint, but does not explicitly contrast it with sibling tools like 'code_quality' or 'standards_check', which could be confused for similar 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?

There is no guidance on when to use this tool versus the many sibling tools. The description does not mention prerequisites, exclusions, or alternative tools for different scenarios (e.g., security scanning vs. linting). An agent has to infer its applicability from the name alone.

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