delimit_repo_diagnose

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

The description lacks any detail about behavioral traits such as side effects, permissions, rate limits, or what exactly 'diagnose' entails. With no annotations, the burden falls entirely on the description, which fails to disclose even basic behavioral information.

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 short (one sentence), but it sacrifices necessary information for brevity. While front-loaded, it is not 'appropriately sized' as it omits crucial context for agent decision-making.

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 presence of an output schema, return values may be covered, but the description fails to provide sufficient context about the tool's behavior, usage guidance, and differentiation from siblings. It is incomplete for a tool with many similar siblings.

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% for the single parameter, which already includes a clear description ('Repository path.'). The tool description does not add any extra meaning beyond the schema, meeting the baseline for high coverage.

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 uses a specific verb 'Diagnose' and resource 'repository health issues', clearly stating the tool's purpose. However, it does not differentiate from the sibling 'delimit_diagnose' which might have overlapping functionality, so purpose clarity is slightly diminished.

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 guidance on when to use this tool versus alternatives. No context about prerequisites, typical scenarios, or exclusions is provided, leaving the agent without decision support.

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