lint_paths

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

Describes the core action (scan every file matching a glob) and return shape. While no annotations exist, the description implies a read-only operation without side effects. Could mention potential resource constraints or glob evaluation behavior.

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 front-loading the action and return type. No extraneous 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 the tool has one parameter and an output schema, the description adequately covers the purpose and return shape. Missing details like glob syntax or edge cases, but still functional for its simplicity.

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?

With 0% schema description coverage, the description only says 'a glob' for the pattern parameter. Does not specify glob syntax, workspace location, or any constraints; relies on user understanding of glob patterns.

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 it scans files matching a glob pattern and returns a structured result with ok/parse_error/findings per path. Distinct from sibling tools that operate on single files or code snippets.

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 for batch scanning via glob, but no explicit guidance on when to use this tool vs. alternatives like lint_file or lint_code. No exclusion criteria or suggested use cases.

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