panelica_git_post_v1_git_repositories_id_rollback

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

Annotations already declare readOnlyHint=false and idempotentHint=false, and the description adds 'Mutating: changes server state' and 'Required scopes: git:write', which is useful but partly redundant with the mutation flag. There is no explanation of consequences, prerequisites, or rollback behavior beyond the fact that it changes state; this is consistent with the annotations and not contradictory.

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 short and front-loaded with the action, followed by route, scope, and mutation metadata. Most lines earn their place, though 'Category: Git' adds little beyond what the endpoint path already conveys.

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 mutating endpoint with an open body schema and no output schema, this description is too sparse. It does not explain what rollback does to the deployment, what body fields an agent should supply, what successful or failed outcomes look like, or any caveats an agent must know before invoking it.

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 schema has only two parameters, and the description adds no meaning beyond the id path parameter shown in the HTTP route. The body parameter is described in the schema as 'not statically declared — see API docs', but the description does not compensate by hinting at what a rollback request body might contain, making correct invocation difficult.

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 opens with the specific verb+resource pair 'Rollback deployment' and reinforces it with the HTTP path POST /v1/git/repositories/:id/rollback, so an agent can identify the action and target resource. It is distinguishable from deploy, pull, and fetch siblings by the rollback verb, though it does not elaborate on what rollback actually entails.

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 given on when to use this tool instead of alternatives such as deploy, fetch, pull, or the Laravel rollback endpoint. The scopes and mutating flag describe the operation but do not help an agent choose it over sibling Git operations.

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