Stories: Update Task

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

Annotations do not provide any hints (readOnlyHint=false, destructiveHint=false). The description only says 'update' without disclosing behavioral traits like whether it replaces or merges fields, permissions needed, or side effects.

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 sentence, which is short and clear. However, given the tool has 5 parameters, it could benefit from slightly more structure without being verbose.

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?

The description does not explain the update semantics (partial vs. full), does not mention return values, and lacks context about required permissions. With no output schema and minimal annotations, the description is insufficient.

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 has 100% description coverage, so each parameter is documented. The tool description adds no additional meaning beyond what the schema provides, earning a baseline of 3.

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 uses the specific verb 'Update' and clearly identifies the resource as 'a task in a story'. Among siblings like stories-add-task and stories-update, this tool is distinct in that it updates an existing task within a story.

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 versus alternatives. No prerequisites, when-not-to-use, or context about updating vs. adding tasks is provided.

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