othos_ticket_update

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

Discloses that the MCP converts the description to TipTap JSON, which is beyond the schema. However, it does not clarify whether updates are partial or full, nor the outcome for other fields beyond description.

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?

Two sentences with no wasted words. First sentence states purpose, second adds critical behavioral detail about description conversion. Highly concise.

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 9 parameters, 4 required, and no output schema, the description is incomplete. It lacks return value info, error cases, and prerequisites. Only description parameter gets behavioral context.

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 only 22%. The description adds meaning for 'description' parameter (format conversion) but provides no additional semantics for the other 8 parameters, failing to compensate for low schema coverage.

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 'Update a ticket's details', specifying the verb and resource. It does not explicitly differentiate from sibling tools like ticket_move or ticket_assign_member, but the focus on updating general details is clear.

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 ticket_move or ticket_assign_member. No mention of prerequisites or context for use.

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