jira_create_subtask

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

The description mentions routing and authorization (JWT, tenant, company scope), but does not disclose that the tool creates a subtask (a write operation), what side effects occur, or any important behavioral traits. With no annotations, the description carries the full burden and fails to disclose mutation.

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 short (3 sentences) and uses little space, but it is not front-loaded with purpose. The first two sentences are technical routing details rather than a clear statement of functionality.

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 that this is a creation tool with an output schema and no required parameters, the description should explain what is created, whether a parent issue is needed, and what the return value represents. It provides none of this context, making it incomplete for effective agent use.

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 single parameter 'arguments' is described as 'JSON string of arguments for the connector operation', which adds minimal meaning beyond the schema's type and title. Since schema coverage is 0%, the description should compensate, but it offers no details on expected structure or keys.

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 merely restates the tool name as 'Jira connector operation `create_subtask`' without defining what a subtask is or how it differs from creating an issue. It adds no functional purpose beyond the name itself.

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 provided on when to use this tool versus alternatives like `jira_create_issue` or `jira_add_comment`. The description lacks any context about prerequisites or scenarios.

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