layerfs_branch_diff_commits

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety is covered. The description adds behavior annotations cannot: results are paginated and continuation is done by feeding the returned cursor back in, plus hunks=false suppresses line-level detail — genuinely useful context for a read-only paging tool with no output schema.

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 tight, front-loaded sentences with no filler — purpose first, then paging and hunk behavior. Minor deduction because the undefined 'nextCursor' token could confuse an agent wiring the cursor parameter.

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 six-parameter, no-output-schema tool, the description leaves two parameters (pagePos, pageSize) and the default hunks behavior unexplained, and never states the shape of returned paths/hunks. Adequate for invoking the tool but with clear gaps an agent may hit on the first call.

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 0%, so the description must compensate with six parameters. It adds meaning for from/to ('saved refs'), cursor (continuation), and hunks (omits line hunks), but pagePos and pageSize go completely undocumented, and the term 'nextCursor' does not appear in the schema, leaving the continuation contract slightly ambiguous.

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?

States a specific verb and resource: paging changed paths between two refs. An agent can grasp what it returns, but the description never contrasts it with near siblings like layerfs_branch_diff_branches or layerfs_fs_diff_files, so differentiation is left to inference.

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?

Implies usage through 'between two saved refs' (both refs must already exist) and gives operational hints for continuation and hunk suppression. However, it offers no when-to-use or when-not guidance relative to the other diff/commit tools in the sibling list.

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