create_problem

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

No annotations are provided, and the description does not disclose behavioral consequences such as required permissions, side effects, or the shape of the response. It merely states 'Create a new problem' and lists parameters, which is insufficient for a mutation tool.

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 concise and front-loaded with the core action, followed by a straightforward argument list. Each line serves a purpose, though the list format is slightly redundant with the schema structure and some parameter labels are minimal.

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?

While an output schema exists and parameter semantics are covered, the lack of usage guidance and behavioral transparency leaves significant gaps. The agent cannot fully anticipate the tool's behavior or when to select it among many siblings, making the description incomplete 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 description compensates for the 0% schema description coverage by explaining all 8 parameters with meaningful labels, including enum mappings for priority, impact, and status, and noting that description is HTML. However, some entries like 'subject: Problem subject' and 'requester_id: Requester ID' are somewhat tautological, preventing a 5.

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 opens with 'Create a new problem,' which is a specific verb and resource. It clearly distinguishes itself from sibling tools like create_ticket, create_change, and create_asset by focusing on the problem entity.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, no exclusions. The description simply states the action and lists arguments, leaving the agent without context on when create_problem is appropriate.

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