gitlens_commit_composer

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

Annotations indicate readOnlyHint=true, which implies no destructive actions; description aligns by saying 'organize' but doesn't clarify if commits are actually created or only message suggestions. No contradiction found between annotations and description.

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?

Two concise sentences that directly state purpose and usage hint, with no redundant or filler content.

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?

Defines purpose and hints at usage, but lacks details on output format or behavior when no changes are detected; no output schema provided, so description could be slightly more complete.

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% and the parameter descriptions are detailed, especially the 'instructions' parameter which includes usage examples and warnings about proper use, adding value beyond the schema.

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 organizes changes into well-formed commits with clear messages, and distinguishes from siblings like git_add_or_commit by focusing on composing commits rather than executing the full workflow.

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?

Suggests it's 'useful for breaking large changes into smaller commits' but does not specify when not to use it, prerequisites, or compare with alternatives like git_add_or_commit or gitlens_start_review.

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