delimit_diagnose

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

With no annotations provided, the description carries the full burden. It discloses side effects: normal mode fixes configuration drift and writes a manifest, dry_run is read-only, and undo reverts changes. This is good, but could be more explicit about permissions or data scope.

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?

Well-structured with clear labeled sections (When to use, When NOT to use, Sibling contrast, Side effects). Every sentence adds value without redundancy. Length is appropriate for the complexity.

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 that an output schema exists, the description adequately covers purpose, usage, side effects, and parameter behavior. It mentions the areas checked (MCP connectivity, deps, governance, etc.), providing a complete picture for a diagnostic tool.

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 coverage is 100%, giving baseline 3. The description adds value by explaining the effects of dry_run and undo in the 'Side effects' section, and noting the default for project_path. This goes beyond the schema descriptions.

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 it is a comprehensive health check of the Delimit installation ('delimit doctor'), using a specific verb and resource. It distinguishes itself from sibling tools like delimit_repo_diagnose (repo-level) and delimit_quickstart (first-run), making its purpose unambiguous.

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 provides when to use (universal first-step diagnostic for installation-wide issues) and when NOT to use (repo-level health or first-run discovery), including specific alternative tool names. This gives clear, actionable guidance for selection.

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