manage_commits

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

With no annotations provided, the description carries full burden but only states what actions are available without disclosing behavioral traits. It doesn't mention whether operations are read-only or mutating, authentication requirements, rate limits, pagination behavior (though schema hints at it), error conditions, or what the outputs look like.

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 a single, efficient sentence that directly states the tool's purpose. It's appropriately sized and front-loaded with the core information, though it could be slightly more specific about the resource context.

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?

For a complex tool with 11 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain the relationships between actions and parameters, what results to expect, or important behavioral aspects. The schema handles parameter documentation, but the description fails to provide necessary context for proper tool selection and usage.

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 schema already documents all 11 parameters thoroughly. The description adds no additional meaning about parameters beyond what's in the schema, so it meets the baseline of 3 where the schema does the heavy lifting.

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 states it's a 'unified tool for listing and getting commits, diffs, and diffstats' which provides a general purpose but lacks specificity about what resources it operates on (commits in a repository). It doesn't distinguish itself from sibling tools like 'manage_source' or 'manage_repositories' that might handle similar operations.

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?

No guidance on when to use this tool versus alternatives is provided. The description mentions multiple actions but doesn't explain when to choose one action over another or how this tool relates to sibling tools like 'manage_source' or 'manage_pull_requests' that might handle related operations.

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