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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds the backing HTTP route, which is mild context, but says nothing about pagination, result ordering, or what 'recorded' branches means for deleted/merged ones; with no output schema, return-shape disclosure would have been valuable.

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 short sentences, front-loaded with the action and resource, with no filler. The second sentence (raw REST path) is marginally useful context for agents that already know the underlying API but is not load-bearing for invocation.

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 simple two-parameter read with full annotation coverage, this is minimally adequate. What is missing is disambiguation from the similarly named 'branches.list' sibling and any note on pagination or result limits, which matters given that no output schema exists.

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 100%, so the two required parameters (organization_id, project_id) are already documented, albeit only as boilerplate restatements. The description adds no format, sourcing, or scoping detail beyond what the schema supplies, so the baseline of 3 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 states a specific verb and resource ('List recorded branches for a project') and scopes it to a project, which is more than a restatement of the name. However, it offers no differentiation from the near-identical sibling 'branches.list' (nor from branch.diff/branch.merge), so an agent cannot confidently choose this tool over that one from the description alone.

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?

There is no when-to-use guidance, no prerequisites or permissions noted, and no mention of alternatives such as branches.list. The only implicit guidance is the project scoping, which the schema already enforces via required parameters.

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