Stories: Assign Current User

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

The description merely states the action 'assign' without revealing behavioral traits beyond what annotations already imply. It does not explain whether the assignment replaces an existing owner, if it can be undone, or what happens if the story already has an owner. With annotations present but not adding detail, the description fails to enrich transparency.

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 extremely concise with a single sentence. It is front-loaded and directly states the purpose. However, it could be slightly more informative without losing brevity.

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 simplicity (one parameter, no output schema, annotations present), the description is minimally adequate. It covers the basic action but lacks contextual details about behavior, usage conditions, and alternatives, reducing completeness.

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 input schema fully covers the single parameter 'storyPublicId' with a description 'Story ID'. The tool description adds no additional meaning or context about the parameter, so baseline score of 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?

The description clearly states the verb 'assign' and the resource 'current user as story owner'. It unambiguously describes the tool's function and distinguishes it from siblings like 'stories-unassign-current-user' and 'stories-update'.

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?

No guidance is provided on when to use this tool versus alternatives such as 'stories-update' (which could also change owner) or 'stories-unassign-current-user'. There is no mention of prerequisites, like the user needing to be a member of the project.

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