delimit_impact

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

Discloses read-only side effects and the backend call (backends.gateway_core.run_impact). Lacks mention of authentication or rate limits, but with no annotations, this is transparent enough.

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?

Four sentences efficiently covering purpose, usage, sibling contrast, and side effects. Front-loaded with key action. No superfluous text.

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 output schema exists, description sufficiently covers purpose, usage, and side effects. Sibling contrast and backend call reference enrich 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 covers both parameters at 100%. Description adds context about dependency manifest scanning and clarifies default behavior for dependency_file (backend default path).

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 the tool analyzes downstream impact of an API change, is informational only, and distinguishes from siblings like delimit_lint which returns pass/fail.

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?

Explicitly states when to use (assessing blast radius for a planned API change) and when not to use (for gate decisions), with named alternatives (delimit_lint, delimit_gov_evaluate).

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