create_tag

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

With no annotations, the description carries the full behavioral burden, yet 'Create a git tag' omits key traits: whether it produces a lightweight or annotated tag, whether the tag is pushed to the remote, whether an existing tag name errors or is overwritten, and what permissions are needed. It adds only the targeting concept.

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?

A single compact sentence with the resource and target front-loaded and zero filler. It is efficient, though it is arguably under-specified rather than perfectly sized for a mutation tool.

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 tool is simple, the schema is fully documented, and the missing return value is excusable given a straightforward create operation. Still, with no annotations and no output schema, the description should have covered whether a message makes the tag annotated and whether the tag is pushed — gaps that matter for correct invocation.

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 all four parameters (including examples for ref, tag_name, project_id) are already documented in the schema. The description's 'pointing to a branch or commit' marginally reinforces the ref semantics but adds nothing beyond it; baseline 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?

States a specific verb and resource ('Create a git tag') plus the target ('pointing to a branch or commit'), which cleanly separates it from list_tags and the release/snippet siblings. It stops short of naming a sibling or scoping the operation to a project, so it is clear but not maximally differentiated.

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 guidance on when to reach for this tool versus create_release (which also creates tags) or how it relates to list_tags. No prerequisites, no conditions, no exclusions are stated.

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