jira_create_subtask

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

Annotations only include readOnlyHint=false, so the description carries the burden. It discloses that the tool automatically determines project and subtask issue type, and controls description format. However, it doesn't mention required permissions, error handling (e.g., if parent issue doesn't exist), or return behavior.

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 two sentences: first states purpose, then lists supported attributes. It is front-loaded and contains no wasted words. Every sentence adds value.

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 8 parameters, 2 required, no output schema, the description covers core functionality well. It explains automatic project/type assignment and description format options. However, it lacks mention of what the tool returns (likely the subtask key), which would improve completeness.

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?

All 8 parameters have descriptions in the schema (100% coverage), so the baseline is 3. The description adds value by explaining the 'format' parameter in detail (e.g., conversion behavior) and listing key optional parameters, but does not significantly enhance the meaning of other parameters beyond the schema.

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 subtask under an existing parent issue', distinguishing it from siblings like jira_create_issue by specifying 'subtask' and 'parent issue'. It also lists supported attributes (priority, assignee, labels, components), making the purpose unambiguous.

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 indicates when to use the tool (to create a subtask) and mentions automatic project/issue type determination, which helps avoid misuse. It does not explicitly state when not to use it or name alternatives (e.g., jira_create_issue for top-level issues), but the context of 'subtask' implies the boundary.

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