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

With no annotations, the description fully carries the behavioral burden, and it does so well. It explains that the test suite is a safety gate, that failures revert all changes, that branch commits/pushes persist if only PR creation fails, and that human merge is always required.

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 somewhat long but every sentence earns its place, covering prerequisites, side effects, failure modes, and parameter meaning. The critical safety guarantees are front-loaded, and there is no filler.

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 tool with one optional parameter and an output schema, the description is remarkably complete. It covers prerequisites, refused inputs, failure behavior, push semantics, and merge policy, so an agent has enough to call it correctly without additional context.

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 description coverage is 0%, but the description compensates by explaining repo_path as a real git repository with a clean working tree and noting uncommitted changes are refused. This adds meaningful semantics beyond the bare schema field, though it does not mention optionality/default behavior beyond what the schema already shows.

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's specific action: propose a real branch and PR that removes unused imports from a Python repository. It adds precise scoping (single-name import lines, >=90% vulture confidence) that makes its purpose concrete and distinct from a general cleanup tool.

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 description implies usage context by specifying criteria for eligible imports and requiring a clean git repository with a full test suite. However, it never explicitly addresses when to use this tool versus scan_dead_code or mentions exclusions, leaving the routing partially to inference.

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

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

With no annotations present, the description carries full burden and does so well: it states the tool is read-only, never modifies anything, and describes the exact output (human-readable findings or 'No real candidates found.'). It also discloses the pyproject.toml dependency for deptry and explains the confidence threshold's trade-off. No annotation contradiction.

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 compact—three sentences for behavior plus two parameter explanations—and all content earns its place, with read-only status front-loaded.

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 two-parameter tool with an output schema and a single sibling, this description covers input semantics, prerequisites, behavioral safety, and result format. The only omitted piece is explicit sibling differentiation, which belongs to usage guidelines. Combined with schema and output schema, an agent has everything needed to invoke it correctly.

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 has 0% description coverage, and the description fills in all of it: repo_path is the path to the repository and must contain pyproject.toml for dependency checks, and min_confidence maps to vulture's 0-100 threshold with a false-positive trade-off. This goes well beyond the parameter names and defaults.

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 opens with a specific verb-resource pair: scan a Python repository, and names the two tools (vulture, deptry) and the two classes of findings (dead code, dependency issues). This clearly distinguishes it from the sibling propose_removal_pr, whose action is proposing a PR, not scanning.

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 explicit guidance on when to use this tool versus propose_removal_pr, nor any when-not conditions. However, the read-only declaration and human-readable output imply this is an analysis step, and the requirement about pyproject.toml provides some context. This makes usage predictable but not explicitly ruled for alternatives.

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