othos_ticket_create

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

With no annotations, the description carries the full burden. It discloses one key behavioral trait: the MCP converts description formats to TipTap JSON. However, it omits other relevant behaviors such as authentication requirements, side effects (e.g., ticket creation triggers notifications), or the response format.

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 extremely concise, consisting of two short sentences. The first sentence states the core purpose, and the second adds a valuable implementation detail. No wasted words.

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?

For a tool with 8 parameters and no output schema, the description is insufficient. It does not explain the return value, constraints on parameters (e.g., priority enum, numeric range for order), or any side effects. The behavioral detail on description conversion is helpful but not enough to provide a complete picture.

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 description coverage is low at 38%. The description adds no new meaning beyond what is already in the schema's parameter descriptions (e.g., the description parameter's format details are repeated from the schema). Other parameters like title, columnId, priority, etc., receive no additional semantic context from the description.

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 explicitly states 'Create a ticket in a column,' which is a specific verb-resource pair. It clearly distinguishes from sibling tools like othos_ticket_update, othos_ticket_delete, etc.

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 is provided on when to use this tool versus alternatives (e.g., othos_ticket_update for modifications, othos_ticket_get to retrieve). The description does not include any usage context or exclusions.

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