recent_changes

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

With no annotations, the description must disclose behavioral traits. It mentions 'local' and 'bounded output,' hinting at no network use and a limit, but it does not explicitly state that the operation is read-only, revertible, or what side effects (if any) it has. This is insufficient for a tool without annotation support.

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, clear sentence with no unnecessary words. 'Bounded output' packs a useful constraint into two words. It is appropriately concise and front-loaded with the action and resource.

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?

There is no output schema or annotations, so the description should explain what the output looks like and how parameters affect behavior. It does not describe return fields, pagination, or the effect of the limit parameter. It also fails to mention the cwd parameter, leaving important context missing for a tool of this complexity.

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?

The schema description coverage is 50% (cwd has a description, limit does not). The description adds only the phrase 'bounded output' which vaguely relates to the limit parameter but does not explicitly explain how to use either parameter or what cwd does. It adds minimal 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 "List recent local Git commits with bounded output" clearly states the tool's action (list), the resource (recent local Git commits), and a key constraint (bounded output). This distinguishes it from sibling tools like repository_summary or file_hotspots, making its purpose unambiguous.

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 is provided on when to use this tool versus alternatives. It does not mention when not to use it or suggest sibling tools. The description simply states the function, leaving the agent to infer usage context from the name alone.

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