create_epic

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

Annotations indicate destructive hint true; description adds detail on side effects: ID assignment, directory/file creation, index registration. Adds context beyond annotations without contradiction.

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?

Two sentences: purpose then action sequence and return value. No fluff, front-loaded with key 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?

Covers return value and side effects comprehensively for a create operation. Lacks error conditions but acceptable given annotations and schema richness.

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 coverage is 100%; description adds value by noting the description parameter is written into epic.md file. Otherwise aligns with schema descriptions.

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 'Create a new epic' and the resource. Distinguishes from siblings like 'create_story' and 'bulk_update_epics' by specifying it creates a single epic with ID assignment and file creation.

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 no explicit when-to-use or alternatives. Implicitly for creating a single epic, but no guidance on when to use this versus sibling tools like 'create_story'.

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