delimit_repo_config_audit

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

Discloses read-only side effects, behavior with remote inputs (shallow clone), and internal implementation call. With no annotations, the description fully informs about behavioral traits.

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 sections, concise sentences, and front-loaded purpose. No unnecessary words.

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 the simple input schema and presence of output schema, the description covers all necessary context: purpose, usage boundaries, side effects, input variations, and experimental status. Complete.

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?

Description adds value beyond the input schema by explaining that target accepts local path, 'owner/repo' shorthand, or GitHub URL. The schema had 100% coverage, but description clarifies input types.

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 audits repository configuration for compliance, listing specific compliance aspects (required files, branch protection, license header). It distinguishes from siblings by naming delimit_repo_config_validate and delimit_repo_analyze.

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' and 'When NOT to use' sections, naming alternative tools for other use cases. This gives excellent guidance.

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