createIssue

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

The description only states 'Create issue', which implies a mutation, but provides no behavioral details such as required permissions, whether it is destructive, or any side effects. With no annotations provided, the description fails to disclose important behavioral traits.

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 (two words), but this is under-specification rather than effective conciseness. It lacks structure and does not use the space to provide valuable 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?

Given the tool's complexity (many nested parameters, no output schema, no annotations), the description is completely inadequate. It provides no context about return values, parameter usage, or essential behavioral constraints, leaving the agent without sufficient information.

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 0%, and the description does not mention any parameters. The input schema contains many nested objects and required fields (e.g., project_id, subject), but the description adds no meaning beyond the schema itself.

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 'Create issue' is clear as a verb+resource, indicating the tool creates an issue. However, it does not differentiate from sibling tools like createIssueCategory or createIssueRelation, and provides no scope or context about what kind of issue.

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 usage guidelines are provided. The description does not specify when to use this tool versus alternatives like updateIssue or getIssues, nor does it mention any prerequisites or context.

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