layerfs_project_list_branches

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile needs no repeating. The description does add value by disclosing the pagination contract (hasMore plus items.length), but it never describes what a branch record contains or what the default page size is. That partial disclosure is a 3, not higher.

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 terse sentences, front-loaded with the purpose, with every clause carrying either intent or the pagination rule. There is no filler or restated metadata.

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, yet the description names only hasMore and items and does not say which branch fields come back. Combined with the undocumented pageSize default, an agent can paginate correctly but cannot anticipate the payload.

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?

With 0% schema description coverage, the description must carry the parameter burden, and it only partly covers one parameter. For a pageSize parameter with a documented 1–1000 range and an unstated default, that leaves a critical gap.

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?

"List project branches" gives a specific verb and resource, so the agent immediately knows what it enumerates. It does not distinguish this from sibling branch tools such as layerfs_branch_list_commits or layerfs_branch_fork, so it stops short of full sibling differentiation.

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?

The pagination instruction ('Follow hasMore with pagePos + items.length') implies when to call again, which is real operational guidance. However, nothing states when to prefer this over related tools like layerfs_branch_list_commits or layerfs_operator_workspace_changes, and no prerequisites are mentioned.

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