gitflic_release_create

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is supplied structurally. The description adds nothing beyond that: it does not explain what the destructive aspect means for an existing tag of the same name, what permissions are needed, or how the idempotent hint interacts with "new" release creation. Notably the combination of "create" with idempotentHint=true is left entirely unexplained.

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?

One short sentence with zero padding, so nothing is wasted. However, brevity here reflects under-specification rather than disciplined compression; there is no structure and no front-loaded detail beyond the bare verb phrase.

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?

This is a six-parameter mutating tool with no output schema and a third of its parameters undocumented. A single sentence cannot cover required fields, defaults, or the result of the call, so the definition is not sufficient for an agent to invoke it reliably.

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 only 33%: only raw and tag carry descriptions, while title, project, preRelease and description are bare. The description compensates for none of this, saying nothing about the meaning of title vs description or what preRelease changes about the resulting release.

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?

"Create a new release" names a verb and a resource, so the basic operation is identifiable. But it stops there: it never says what a release actually contains (tag, title, description, pre-release flag) or how it relates to adjacent siblings such as gitflic_tag_create or gitflic_release_edit, so the agent must infer the distinction from names 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 at all: no prerequisites, no mention of which sibling to pick for editing or fetching a release, and no exclusions. The agent gets no help deciding between creating a release and creating a tag or a branch.

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