update_epic

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

The description adds the WRITE_ENABLED=true requirement beyond what annotations provide. Annotations already cover readOnly=false, destructive=false, and idempotent=true, so the additional prerequisite is valuable. No contradiction with 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?

The description is a single sentence with no unnecessary words. The parenthetical is concise and adds relevant context without bloat.

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 simple update operation with two well-documented parameters and annotations providing safety profile, the description is adequate. It doesn't mention return values or failure modes, but these are not critical given the straightforward nature and complete 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?

Schema description coverage is 100% with both 'fields' and 'sys_id' described. The tool description adds no additional parameter meaning, so the baseline score applies.

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?

Clearly states the action 'Update' and the resource 'an epic', distinguishing it from create_epic and list_epics. The parenthetical prerequisite doesn't obscure the primary purpose.

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?

Provides a clear prerequisite (WRITE_ENABLED=true) which is useful context for when this tool can be used. It doesn't explicitly compare with alternatives like update_story, but the resource-specific nature makes the usage context clear.

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