delimit_repo_diagnose

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

Discloses read-only nature, requirement of 'require_premium', internal implementation call, and experimental status. With no annotations, this fully covers behavioral transparency.

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?

Concise yet structured with clear sections (when to use, when not, sibling contrast, side effects). Every sentence provides value.

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?

Complete for a simple diagnostic tool: covers when to use, behavior, side effects, gating, and experimental status. Output schema exists so return values need not be explained.

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 input schema already describes the single parameter 'target' with default and path explanation. The description adds no further detail beyond the schema, meeting the baseline for full coverage.

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 'Diagnose repository health issues' and distinguishes from siblings by specifying when to use delimit_repo_analyze and delimit_repo_config_validate instead.

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 (before commit/push), when not to use (for full analysis or per-file validation), and provides sibling contrast with delimit_repo_analyze.

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