Add followup to ticket

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the write-and-non-idempotent profile is covered structurally. The description adds nothing beyond that: it does not warn that repeated calls create duplicate followups, does not mention the private/public visibility effect, and does not state permission requirements.

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 single sentence is free of padding and front-loaded, which is good. But its brevity here stems from under-specification rather than disciplined editing, so it lands at an adequate-but-thin 3 rather than a 5.

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 four parameters, an output schema, and annotations in place, the structured metadata carries most of the load, but the description still omits the sibling routing and the duplicate-followup behavior an agent should know before calling. For a mutation tool in a family of near-identical followup tools, this is a meaningful gap.

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 100%, so all four parameters (content, ticketId, users_id, is_private) are already documented in the schema, including defaults and the 1/0 privacy convention. The description adds no parameter-level meaning beyond what the schema provides, making the baseline 3 correct.

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 gives a clear verb ("Add") and resource ("comment/followup to a ticket"), so the agent knows exactly what the tool produces. It does not, however, differentiate itself from the several sibling followup tools (glpi_add_problem_followup, glpi_add_change_followup), which is the only thing keeping it from a 5.

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 when-to-use guidance, no prerequisites, and no mention of the alternative followup tools that exist for problems and changes. The agent must infer from the name alone that this is ticket-scoped rather than problem- or change-scoped.

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