code_inspect_heavy_dependencies

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

No annotations are provided, so the description carries the burden. The verb 'Inspects' clearly signals a read-only analysis rather than a mutation, and 'with optimization tips' discloses the deliverable. It does not explicitly say the tool never modifies anything, but 'inspects' makes that interpretation reasonable.

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?

A single sentence that front-loads the verb and resource, then adds specific examples and the expected deliverable. There is no filler or redundant restating of the tool name.

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?

For a simple one-parameter inspection tool this is mostly sufficient. The main gaps are the absence of an output schema or clearer return-value description beyond 'optimization tips', and no guidance for the case where projectPath is omitted, especially since the schema lists no required parameters.

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 only parameter, projectPath, is already documented in the schema with 100% coverage ('Path to project root with package.json'). The tool description adds no additional parameter-level meaning, so the baseline of 3 applies.

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 ('Inspects'), a concrete target ('package.json'), and a precise outcome ('identify bloated dependencies' with optimization tips). The named examples sharpen the scope and distinguish it from sibling tools like perf_audit_assets or doctor_diagnose_project.

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?

Usage is implied: call this when auditing package.json for oversized dependencies and optimization advice. However, it never states when not to use it or which alternative to prefer, leaving routing partly to the agent.

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