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

Annotations already declare non-readOnly, non-destructive, non-idempotent, closed-world, so the safety profile is covered. The description adds genuinely useful behavior an agent could not get elsewhere: default status DRAFT, authorship by the agent bot user, and emission of an EPIC_CREATED activity event — side effects worth knowing about.

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?

Three short sentences, front-loaded with the create action, then defaults and attribution. Every clause carries distinct information: entity type, default status, field mapping, actor, and event side effect.

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 three-parameter mutation with no output schema, the description covers defaults, authorship, and side effects, which is most of what an agent needs. It omits error/duplicate-name behavior and what the response contains, so not fully complete but solid.

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 only 33%, so the description has to carry weight; it does explain that 'description' maps to the artifact content field and reframes projectId as 'the given project'. However it says nothing about the name parameter's role or the length limits beyond what the schema already encodes, leaving one gap.

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?

States a specific verb and resource and pins down the underlying entity ('an Artifact with artifactType=EPIC'), which separates it cleanly from siblings like create_story, create_defect, create_test_case. No ambiguity about what is being produced.

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?

Scope is implicit: it creates an epic 'in the given project', which implies project membership is required, but there is no explicit when-to-use-this-vs-another statement (e.g. epic vs story vs defect). Usage is inferable from the name and first sentence rather than stated.

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