create_ticket

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

No annotations provided, and the description only states the action. It does not disclose behavioral traits such as authentication requirements, rate limits, or consequences of creation (e.g., ID generation, potential duplicates).

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 a single, focused sentence without fluff. It is concise, but could be more informative without sacrificing brevity, e.g., mentioning the required fields.

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 nested input schema and no output schema, the description is insufficient. It does not explain return values, error handling, or integration context, leaving the agent underinformed for a create operation.

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 comprehensive descriptions for each property (e.g., 'The ticket summary'), so the description adds no value beyond the schema. With schema coverage effectively high, a baseline score of 3 is appropriate.

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?

Description 'Create a new Jira ticket' clearly states the action and resource. However, it does not differentiate from sibling tools like batch_create_issues, which also creates tickets. A more precise scope (e.g., single ticket creation) would improve clarity.

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 on when to use this tool versus alternatives like batch_create_issues or update_ticket_fields. The description lacks explicit context for selection, leaving the agent to infer.

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