pylon_create_issue

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

With no annotations present, the description carries full burden for behavioral disclosure. It only indicates a write/mutation operation ('create') but omits details on side effects, authentication requirements, rate limits, idempotency, or what happens on duplicate attempts.

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, clear sentence with no unnecessary words. However, it could be slightly more informative without sacrificing conciseness, such as mentioning the output or required parameters.

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?

The description lacks information about return values (e.g., does it return the created issue?), error conditions, or behavior when required fields are missing. Given the complexity of 5 parameters and no output schema, more detail is needed for complete understanding.

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 descriptions cover 'status', 'priority', and 'assignee' (60% of parameters), but 'title' and 'description' lack any schema description. The tool description adds no additional meaning for these parameters, failing to clarify expected input format or constraints.

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 action ('Create') and the resource ('support issue/ticket in Pylon'), effectively distinguishing it from sibling tools like pylon_update_issue or pylon_get_issue. The verb-resource combination is specific and 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 provides no guidance on when to use this tool versus alternatives such as pylon_create_contact or pylon_update_issue. It does not mention prerequisites, context for creation, or when to choose other tools for related tasks.

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