Publish release notice

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

Beyond the annotations (readOnlyHint=false, etc.), the description discloses the crucial behavioral trait of the dry-run fallback when RELEASE_WEBHOOK_URL is missing. It also mentions 'Normalize,' implying input transformation. However, it does not mention error behavior or side effects of the webhook call itself.

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 concise sentences, front-loaded with the primary purpose, and includes an important conditional in the second sentence without any redundant or filler content.

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 simple parameter set and no output schema, the description covers the essential operational context (normalization, publishing, dry-run behavior) sufficiently. It doesn't discuss return values or failure modes, but these are less critical for a straightforward publish action.

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 provides full descriptions (100% coverage) for all three required parameters: repository, tag, and summary. The description adds no additional parameter-level detail or constraints, so the baseline score of 3 is appropriate.

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 the action ('Normalize and publish a release announcement') and the target (configured webhook). It also distinguishes behavior based on configuration (dry run without RELEASE_WEBHOOK_URL), making it specific and unambiguous.

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 provides clear context on when the tool publishes and when it performs a local dry run, but it does not explicitly compare against alternatives or state exclusion criteria. Since no sibling tools exist, this is sufficient.

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