gencommit

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

在没有注释的情况下，描述揭示了返回规范说明、步骤、模板和示例，而非最终消息，行为透明。

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?

两句话简洁明了，直接切入主题，没有冗余。

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?

对于两个可选参数且无输出模式，描述已涵盖主要行为，足够完整。

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?

模式覆盖100%，描述未显著增加参数含义，属于基准分。

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?

明确说明用于生成Git commit消息，遵循Conventional Commits规范，与兄弟姐妹工具如add_feature、fix_bug等区别明显。

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?

指出不直接代写最终消息，也不应被判定为空结果，提供了使用上下文，但未明确说明何时不使用。

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