layerfs_branch_list_commits

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered. The description adds meaningful context—newest-first ordering along first parents—but does not disclose pagination defaults, behavior at the end of history, or what a page contains.

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?

A single sentence with no filler, and the key ordering trait is front-loaded after the verb. Slightly terse for the amount of pagination semantics left unstated.

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?

With no output schema, the description is the only place paging semantics could be explained, yet it leaves defaults, cursor-vs-offset meaning, and terminal-page behavior unaddressed. For a paginated list tool with 0% schema coverage, this is a substantial gap.

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% across three parameters, so the description must compensate and largely does not. It implies 'branch' and paging but never clarifies whether pagePos is an offset or cursor, what pageSize defaults to, or the cap of 1000.

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 ('Page') and resource ('a branch's checkpoint history') with an ordering guarantee ('newest first along first parents'). This distinguishes it from nearby siblings like layerfs_operator_store_commits and layerfs_branch_diff_commits, though it does not name them explicitly.

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 (paging a branch's commit history) but gives no explicit when-to-use or when-not-to-use guidance, and never points to an alternative such as branch_diff_commits for comparing histories. The agent must infer the context from the verb alone.

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