delimit_docs_validate

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

No annotations exist, so description carries full burden. It states 'read-only inspection' and mentions the backend call, revealing nondestructive behavior. Could add more detail on output format but output schema exists, so this is sufficient.

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?

Extremely concise: two sentences plus structured sections (when to use, when NOT, sibling contrast, side effects). Every section earns its place with no redundancy.

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 one optional parameter, existing output schema, and no annotations, the description covers usage guidelines, side effects, sibling distinction, and internal call. It is complete for a simple validation 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?

Only one parameter (target) with full schema description (100% coverage). The description does not add new context beyond what the schema provides; baseline of 3 is appropriate.

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 explicitly states it validates documentation quality and completeness, listing specific examples (missing READMEs, undocumented functions, broken links) and directly contrasts with sibling delimit_docs_generate which writes. The verb 'validate' and resource 'docs' are clear and specific.

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?

Provides explicit when-to-use (CI gate for surfacing issues) and when-not-to-use (avoid for generating API reference, recommending delimit_docs_generate). Also includes sibling contrast, making usage context very clear.

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