create_epic

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions default session behavior and verbosity options, but does not discuss side effects, permissions, rate limits, or any other behavioral traits. This is insufficient for a creation tool.

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 at two sentences, with no unnecessary information. The first sentence clearly states the purpose, and the second adds essential parameter details. Every sentence earns its place.

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 has 5 parameters, 0% schema coverage, and no annotations, the description is incomplete. It mentions session default and verbosity but fails to explain required parameters like project_id and subject, or the flexible 'kwargs' parameter. An output schema exists, so return values are covered, but the description lacks the depth needed for an agent to use the tool correctly without additional context.

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 0% description coverage, so the description must compensate. It only adds meaning for two parameters (verbosity values and default, session default), leaving project_id, subject, and kwargs unexplained. The description adds some value but falls short of providing comprehensive parameter guidance.

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 'Creates a new epic within a project,' providing a specific verb and resource. However, it does not differentiate itself from the sibling tool 'bulk_create_epics', which also creates epics but in bulk. The purpose is clear but lacks distinction from a related tool.

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 given on when to use this tool over alternatives like 'bulk_create_epics' or other creation tools. The description does not specify prerequisites, context, or situations where using 'create_epic' is appropriate or inappropriate.

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