create_tag

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

Annotations already indicate this is a mutating, non-idempotent operation. The description adds useful context by explaining the annotated vs. lightweight tag behavior. It does not disclose failure modes such as duplicate tag handling or permission requirements, but it is not misleading and provides some value beyond the annotations.

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 two sentences long, front-loads the primary purpose, and every sentence adds useful detail. It has no filler and is easy to parse quickly.

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 relatively simple, annotations cover the mutating nature, and an output schema is present. The description explains the core behavioral nuance of annotated vs. lightweight tags. It could be more complete by mentioning what happens if a tag already exists or how this relates to sibling tag/release tools, but nothing essential prevents an agent from using it correctly.

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 20%, so the description partially compensates by explaining the 'message' parameter's role in determining tag type. Other parameters, like repo_owner, repo_name, and tag_name, are self-explanatory from their names, and the schema already documents the 'sha' parameter. Overall, the description adds some meaning but does not fully cover all parameter semantics.

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 uses a specific verb and resource: 'Creates a new tag.' It also adds meaningful distinction between annotated and lightweight tags, which gives the agent a clear idea of what the tool does beyond the name.

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 by stating it creates a tag, and it explains that a message yields an annotated tag while omitting it yields a lightweight ref. However, it does not explicitly discuss when to choose this over sibling tools like delete_tag, list_tags, or create_release, or mention any conditions to avoid using it.

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