Delimit Project Config

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

The description discloses concrete side effects: action='init' writes a new delimit.yml at project_path, while 'load' and 'model' are read-only. This goes beyond the annotations and clarifies the mixed read/write nature of the tool, which is essential for safe invocation.

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?

The description is well-structured with clear sections, front-loads the core purpose, and every sentence adds useful guidance. It is compact despite covering usage, exclusions, sibling contrast, and side effects.

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 tool's multi-action nature and conditional parameters, the description provides complete context: what the tool manages, when to use it, when not to, how it differs from the closest sibling, and what side effects to expect. An output schema exists, so return-value documentation is not required here.

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 description coverage is 100%, so the baseline is 3. The description adds minimal value beyond the schema: it confirms that 'init' writes to project_path and lists the modes, but the schema already documents parameter-specific constraints like 'only for init' and 'only for action=model'.

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 opens with a specific verb and resource: 'Manage delimit.yml project configuration (load / init / model).' It names the exact file and modes of operation, and the sibling contrast explicitly distinguishes it from delimit_gov_status, so an agent can tell them apart.

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?

The description provides explicit 'When to use' and 'When NOT to use' guidance, naming delimit_gov_status and delimit_playbook as alternatives for governance state and prompt management. This fully routes the agent to the correct tool.

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