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

Goes well beyond the annotations: it enumerates the side effects (branch, commit to .stride/<KEY>.md, draft PR, auto-link back to story), explains concretely what idempotentHint means (returns the existing open draft PR if one is linked), and discloses the auth prerequisite. With readOnly=false and openWorld=true already declared, this is exactly the extra context an agent needs before a write to an external system.

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?

Front-loads the outcome and the artifact chain, then usage and constraints. The repo/baseBranch/identifier sentences largely duplicate the schema descriptions, which is minor waste in an otherwise tight definition.

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?

No output schema exists, and the description partly compensates by saying it returns the existing open draft PR on re-invocation. It stops short of saying what the successful result contains (PR URL/number, branch name), which would fully close the gap.

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% and every parameter already has a description, so the description only restates the storyId formats, repo form, and baseBranch default. It confirms rather than adds meaning; baseline 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?

States a concrete verb and artifact chain: opens a branch named with the ticket key, commits the spec to .stride/<KEY>.md, and opens a draft PR. No sibling tool in the list creates PRs, and the description's focus on 'DRAFT pull request from a story' makes the resource 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?

"Use after implementing a story to create the review surface" gives a clear trigger, and the GitHub-connection prerequisite is stated explicitly. It doesn't name a when-not condition or an alternative path, but no sibling tool offers a comparable capability.

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