github_create_tag

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

With no annotations, the description carries the full burden. It discloses the core behavior and the conditional annotated tag creation, but does not mention authentication requirements, what happens if the tag already exists, or other side effects. This is better than a bare 'Create tag' but lacks richer context.

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 concise and well-structured: a one-line purpose followed by a clean Args block. Every line adds value, and the front-loaded purpose makes it immediately clear what the tool does.

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 tool's simplicity and the presence of an output schema, the description covers the essential inputs and behavior. It lacks explicit prerequisites or error conditions, but these are not critical for a basic create operation. The parameter semantics and conditional behavior make it sufficiently complete.

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 0%, so the description must compensate. It provides meaningful explanations for all six parameters, including the semantic role of 'sha' and the conditional effect of 'message'. The example for 'tag_name' adds clarity, though some entries are terse.

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 'Create a new tag (lightweight or annotated)' with a specific verb and resource. It distinguishes this tool from siblings like github_create_release and github_create_branch by focusing on tags, including the lightweight vs. annotated distinction.

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?

The description implies usage for tagging a specific commit but does not explicitly discuss when to use this tool versus alternatives like github_create_release or github_list_tags. It provides no exclusions or alternative tool names, only the conditional behavior of annotated vs. lightweight tags.

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