delimit_review

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

The description discloses that the tool sends code to multiple AI models and consolidates feedback, which is valuable. However, with no annotations, it fails to mention potential costs, side effects, or authorization needs, leaving gaps in behavioral understanding.

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 very concise, with three clear sentences. It front-loads the purpose, then explains the multi-model aspect, and finally covers output and input options. 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 tool's complexity (4 optional parameters, no required), the description covers the main purpose and input options. However, it lacks prerequisites or error conditions, and omits details about the output schema despite its existence.

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%, so the baseline is 3. The description adds minimal value beyond the schema, only clarifying that diff and file_path are alternatives. This is not a significant improvement.

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 performs a multi-model code review on a diff or file, which is specific and useful. However, it does not distinguish itself from sibling tools like delimit_diff or delimit_lint, which could confuse agents.

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?

There is no explicit guidance on when to use this tool versus alternatives. The description only mentions the input options (diff or file path) but does not explain the context or exclusions.

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