pm_lint

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

The description discloses that auto-fix is possible and support for multiple checks, but does not explicitly state if the tool modifies files (destructive) or whether it runs both checks by default. No annotations to clarify.

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 efficiently convey the tool's purpose and key capability. No redundancy or unnecessary detail.

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?

Description covers basic functionality but lacks default behavior (no parameters), output expectations, and prerequisites. With no output schema, return value is unclear.

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 covers 100% of parameters; description repeats schema info without adding new semantics beyond confirming 'fix' enables auto-fix and 'format' combines with fix. No additional constraints or examples.

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 runs linting on the project and supports ESLint and formatting checks. It distinguishes from sibling tools like pm_build and pm_test by specifying a different action (linting).

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 guidance on when to use this tool over alternatives (e.g., pm_review_run, pm_test). Does not mention prerequisites or context where linting is appropriate.

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