Create User Story

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

Annotations already indicate this is a write operation (readOnlyHint=false) and non-destructive. The description merely repeats the word 'create' and adds no additional behavioral context such as return values, side effects, or permission requirements. With annotations present, the description contributes nothing beyond them.

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 a single uninformative sentence that essentially restates the title. While it is short, it is under-specified rather than effectively concise; it does not earn its place by adding any useful information.

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 tool with 9 parameters, 2 required fields, nested objects, and no output schema, a one-sentence description is wholly inadequate. It does not mention required inputs, creation behavior, or expected results, forcing the agent to infer everything from the 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?

The description mentions no parameters. With 9 parameters and only 33% schema description coverage, the description should compensate for the undocumented fields but entirely fails to do so. The schema's sparse descriptions for points, watchers, and assigned_to are the only guidance, leaving most parameters unexplained.

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 clearly identifies the action ('Create') and the resource ('user_story'), which distinguishes it from sibling tools like user_story_update or user_story_delete. However, it is extremely terse and lacks any scope or contextual detail, leaving it only minimally helpful.

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?

There is no guidance on when to use this tool, what prerequisites exist (e.g., a valid project and subject), or how it compares to other create tools like task_create or issue_create. The description provides zero usage context.

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