create_release

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

With no annotations provided, the description carries the behavioral disclosure burden. It explains permission requirements, nesting depth constraints, ISO date format expectations, and the independent semantics of isStarted/isCompleted vs startedAt/completedAt. This adds meaningful non-obvious context beyond the tool's name.

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 three short sentences, each with a distinct purpose: stating the action, noting permissions and nesting, and clarifying date/flag semantics. It is front-loaded with the primary purpose and contains no filler or redundancy.

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 complexity (17 parameters) and the high schema coverage, the description fills in critical gaps such as permission roles, nesting constraints, and flag behavior. While it doesn't mention every edge case (e.g., default values or error conditions), the combination of schema and description is sufficient for a create operation with no 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 description coverage is 82%, so most parameters are already documented in the schema. The description adds extra value by clarifying parentReleaseId nesting depth and the relationship between isStarted/isCompleted and startedAt/completedAt, which are not fully explained in the schema.

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 opens with 'Create a new release,' a specific verb + resource that clearly states the tool's function. This distinguishes it from sibling tools like list_releases, get_release, and update_release, which perform different operations on the same resource.

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 practical usage context: it lists required write permissions (org_owner, org_admin, org_member) and explains how to use parentReleaseId for nesting with a max depth of 3 levels. However, it does not explicitly state when to prefer this tool over alternatives, though the name and sibling naming make that obvious.

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