release_notes

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

With no annotations, the description carries the burden of disclosing behavior. It states the tool 'Extract[s]' (implying read-only), 'Categorizes changes', and 'provides writing guidelines', which is useful. However, it does not disclose prerequisites like git installation, error behavior, or whether a Pro subscription is required for execution, leaving some ambiguity.

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 exceptionally concise, consisting of three short sentences that each add distinct value: purpose, behavior, and a key constraint. There is no fluff or redundancy, and the most important information is front-loaded.

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 (3 optional parameters, no output schema), the description provides a sufficient overview: it explains the input (git commits since tag) and output (structured data with categories and writing guidelines). It doesn't detail the exact output structure, but for a tool like this, that level of detail is likely not essential.

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 the baseline is 3. The description adds little beyond the schema—it mentions 'since last tag' in the purpose but does not elaborate on defaults or value formats that the schema doesn't already cover.

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 tool's function with a specific verb ('Extract') and resource ('git commits since last tag'), and directly connects it to writing App Store release notes. It distinguishes itself from sibling tools by focusing on generating structured data for release notes, which is unique among the provided tools.

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 when you need to generate release notes from git history, but it does not provide explicit when-to-use/when-not-to-use guidance or mention alternatives. The 'Pro feature' note is a constraint but not usage guidance.

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