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

Annotations already signal this is a non-destructive, non-idempotent write. The description adds genuinely useful behavior: it returns the new displayId and echoes accepted fields (AC ids, epic/sprint/parent/assignee) so no confirm-read is needed, and that cross-project ids are rejected. This is real value beyond 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?

Front-loads the core action, then the required/optional split, then behavioral notes on status and return values. Slightly redundant in listing every optional param already visible in the schema, but overall dense and efficient.

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 13-param write tool with no output schema, the description supplies the return shape (displayId plus echoed fields) and cross-project validation, which are the key missing structured pieces. A few param-level details remain uncovered, but an agent can call it correctly from this.

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 only 46%, so the description must compensate. It clarifies the status category-vs-board-column alternative and the parentId ticket-key/UUID format, but several params (labels, priority, storyPoints, type, acceptanceCriteria) are left to the schema and their self-evident names, leaving the coverage gap only partially closed.

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 specific verb and resource ('Create a new story in a Stride project') and enumerates the fields it configures, so the agent knows exactly what it produces. It does not explicitly distinguish itself from siblings like create_defect, create_epic, or update_story, which leaves some ambiguity for ticket-shape decisions.

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?

Gives clear operating guidance: required vs optional fields, the status category-or-column rule, and a named alternative (stride.list_workflow_stages) for discovering valid column names. It stops short of explicit when-not-to-use guidance, e.g. against create_defect for bugs or create_epic for epics.

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