Create Jira Product Discovery Insight

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

The description discloses that the server builds a fixed ADF description, uses existing OAuth, and intentionally does not create a structured snippet. This goes beyond annotations (which only indicate write operation, open world, not idempotent). However, there is some ambiguity about how the 'description' parameter is used given the fixed ADF construction.

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 concise, front-loaded sentences. Every sentence adds information: the first states the core action, the second explains server-side behavior and auth. No waste.

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?

With an output schema present, return values need not be described. The description covers key behavioral aspects (ADF construction, OAuth, no snippet). Some side-effect details are omitted, but the description is sufficiently complete for a creation tool with annotations.

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 input schema has 100% coverage with descriptions for all 5 parameters, so the baseline is 3. The description adds minimal new parameter semantics—it mentions summary/quote/linked source but does not clarify the role of each parameter beyond what the schema already provides.

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 the tool creates a 'native Jira Product Discovery Insight' with a specific verb and resource. It distinguishes itself from sibling tools like jira_post by focusing on JPD insights specifically.

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 implies this tool is for creating JPD insights and mentions the use of existing OAuth, but it does not explicitly compare to alternatives like jira_post or state when not to use it. Since siblings include a generic jira_post, more explicit guidance would help.

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