createRelease

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It says nothing about side effects, required permissions, whether the operation is destructive, or what the response would be. The description only warns against a use case, providing zero transparency about the tool's actual behavior.

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 extremely brief (two sentences) and every word is used to redirect the user to alternative tools. It is well-structured for that narrow purpose, but it omits essential purpose information, so it is more under-specified than genuinely concise.

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 tool with 7 parameters, no annotations, and no output schema. The description should explain the tool's purpose, when to use it, and behavioral caveats. Instead, it only provides exclusions and alternative tool names, making it grossly incomplete for a tool of this complexity.

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 input schema already covers 86% of parameters with descriptions, so the baseline is 3. The tool description adds no parameter semantics beyond the schema; it does not mention any of the seven parameters, leaving the schema to carry the weight.

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 never states what createRelease actually does. It only provides a negation ('Not supported for UI release notes') and redirects to alternatives. The name implies creating a release, but the description lacks a clear verb+resource statement, making the tool's purpose ambiguous.

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 gives explicit alternatives for two specific use cases: announceSoftwareFromForgeRelease for Zapstore/NIP-82 APK announce, and listReleases + publishRepoState for git tags. However, it never states the intended use case for createRelease itself, so the positive when-to-use guidance is missing.

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