Collect commits for release notes

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: it returns structured/categorized data, supplies writing guidelines, and is gated as a 'Pro feature' (an entitlement prerequisite). It doesn't describe output shape or pagination, but it goes well past 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?

Two tight sentences with the core action front-loaded and the downstream purpose immediately after; no filler. A touch terse on behavioral detail, but every clause earns its place.

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?

For a no-output-schema, read-only tool with three fully documented optional parameters, the description conveys enough: what it reads, what it returns (structured/categorized data plus guidelines), and the Pro gating. Only the exact return structure is left unspecified, which is acceptable absent an output schema.

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%, so since_tag, max_commits and project_path are fully documented in the schema itself. The description only echoes the date-range concept ('since last tag') without adding syntax or format details beyond what the schema already provides, making the baseline 3 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 gives a specific verb and resource ('Extract git commits since last tag') and states the downstream goal (App Store 'What's New' text), so its function is unambiguous. It does not explicitly differentiate itself from nearby siblings such as release_version or release_preflight, which is the only reason it isn't a 5.

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?

Usage is implied by 'since last tag' and 'for writing App Store What's New text', so the agent can infer the scenario. However there is no explicit when-to-use guidance, no exclusions, and no mention of when a different sibling (e.g. release_version) is the better choice.

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