github_repos_rename_branch

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states 'rename a branch,' which implies mutation but does not clarify side effects, such as whether it triggers webhooks, affects protected branches, or if the old name becomes immediately unavailable.

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 extremely concise (three words) and front-loads the essential action. Every word is meaningful, but it could afford to add a bit more context without becoming verbose.

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?

Given the lack of output schema and the complexity of the 'body' parameter, the description is insufficient for an agent to confidently invoke the tool. It does not explain the return value, required body fields, or error conditions.

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?

The input schema has 100% description coverage, but parameter descriptions are minimal (only parameter names). The description adds no additional meaning beyond the schema. The 'body' parameter is a nested object with no defined properties, leaving its required fields unclear for the agent.

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 'Rename a branch' clearly states the specific verb (rename) and resource (branch). The tool name and description together make the purpose unambiguous, and given the extensive sibling list, the name itself differentiates it from other branch-related tools.

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 guidance is provided on when to use this tool versus alternatives like branch protection updates or simple branch creation. There is no mention of prerequisites (e.g., write permissions, branch existence) or when not to use it.

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