semantic_changelog

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does communicate that the output is human-readable and derived from graph changes, but it omits important behavioral context such as output format, side effects, whether a sync must have occurred first, and how this differs from graph_diff.

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, focused sentence with no filler. Every word contributes meaning, including 'human-readable' and 'between syncs,' which add useful context beyond the name.

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 zero-parameter tool, minimalism is less risky, but the absence of annotations and an output schema means the description should explain what the returned changelog looks like and when it is available. The current text is minimally viable but leaves those details unspecified.

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?

This tool has zero parameters, so no parameter documentation is needed. The empty schema makes coverage trivially complete, and the description introduces no conflicting parameter expectations, so the baseline score applies.

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 that the tool produces a human-readable changelog derived from graph changes between syncs, giving both the output form and the data source. It is distinguishable from the likely raw graph_diff sibling via the 'human-readable' qualifier, though it lacks an explicit action verb like 'generate' or 'return.'

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 like graph_diff, search_history, or sync_repository. The phrase 'between syncs' implies a relationship to synchronization but does not explain prerequisites or exclusion criteria.

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