release_notes

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

No annotations are provided, so the description must fully disclose behavioral traits. It states it returns structured data and provides guidelines, but does not mention that it is read-only, whether it modifies anything, authentication requirements, or the exact structure of the output. This leaves significant gaps for an agent to understand side effects.

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?

Two concise sentences with no superfluous information. The main action is front-loaded, and every sentence contributes to understanding the tool's core purpose.

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?

With no output schema, the description should detail the return format. It mentions 'structured data' and 'categories' but lacks specifics about the response structure. Given the tool's moderate complexity (3 optional params), the description is minimally adequate but could be more 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 coverage is 100% with descriptions for all three parameters. The tool description adds context about git commits and App Store text but does not enhance the parameter meaning beyond what the schema already provides. 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 explicitly states the tool's purpose: extract git commits since last tag, categorize changes, and provide writing guidelines for App Store 'What's New' text. This is a specific verb-resource combination that clearly distinguishes it from sibling tools like 'app_details' or 'release_preflight'.

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 generating App Store release notes but does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites or cases where it should not be used. Context is implied but exclusions and comparisons are missing.

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