create_ticket

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

With no annotations, the description effectively discloses key behaviors: project resolution logic, description format dependency on environment variables, error behavior when ambiguous, and what the tool does not do. Minor omission: no mention of return value or permissions.

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 front-loaded with the main action and uses bold for emphasis. It is concise but dense, packing multiple details into one paragraph. Slight improvement could break into bullet points for clarity.

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 7 parameters and no output schema, the description covers project resolution and description format well. However, it lacks information about the return value (e.g., created ticket key) and does not mention any potential side effects or idempotency.

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?

Input schema has 100% coverage, but the description adds meaning for project and board parameters by explaining resolution strategies and the role of environment variables. It also clarifies description format nuances beyond the schema's plain text description.

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 'Create an issue in a project,' using a specific verb and resource. It distinguishes from sibling tools like edit_ticket and delete_ticket by focusing on creation and providing unique project resolution details.

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?

The description provides explicit guidance on when to use project, boardName, boardId, or omit project, including fallback behavior and error handling. It also advises using list_boards for disambiguation and clarifies that sprint/backlog placement is not set, directing to UI/Agile REST.

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