getRepositoryBranchingModelSettings

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

No annotations are provided, so the description carries full burden for behavioral traits. It does not mention that the operation is read-only, what side effects (if any) exist, or any permissions required. The minimal description adds no behavioral context beyond the implied read nature.

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 concise sentence that conveys the core purpose without redundancy. It is front-loaded and efficient, containing no fluff.

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?

The description does not describe the response format or fields returned, which is important since no output schema is provided. For a configuration retrieval tool, this omission reduces completeness. The high schema coverage partly compensates, but the lack of behavioral or output context leaves gaps.

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 schema already documents both parameters (workspace, repo_slug). The description adds no additional meaning or constraints beyond what is in the schema, achieving the baseline score.

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 the tool retrieves the branching model config for a repository. It uses a specific verb ('Get') and resource ('branching model config'), which helps distinguish it from sibling tools like 'getRepositoryBranchingModel' or 'getProjectBranchingModelSettings'.

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 guidelines are provided about when to use this tool versus alternatives (e.g., 'getRepositoryBranchingModel' or 'getEffectiveRepositoryBranchingModel'). The description lacks context on prerequisites or scenario fit.

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