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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the mutation/safety profile is covered structurally. The description adds the role semantics of the type field, but that information is duplicated in the schema rather than adding new behavioral context such as ordering, duplicate handling, or 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?

Two compact sentences with the core action front-loaded and no filler. The second sentence restates the type mapping already present in the schema, which is minor redundancy rather than bloat.

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 only three fully documented parameters, a present output schema, and annotations covering the safety profile, the description supplies everything an agent needs to invoke the tool correctly. The only gap is that it never distinguishes this from glpi_add_ticket_user.

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 the schema alone documents all three parameters, including the same '1=Requester, 2=Assigned, 3=Observer' mapping the description repeats. Baseline 3 applies since the description contributes no meaning beyond the structured fields.

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?

States a specific verb and resource ('Add a group to a ticket') and enumerates the three relationship roles, so the agent knows exactly what the operation creates. It is clear without opening the schema, though it does not explicitly name the adjacent sibling glpi_add_ticket_user as the alternative for individual users.

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?

Usage is implied by the name and the role list, but there is no explicit when-to-use guidance, no statement of the alternative (glpi_add_ticket_user) or exclusion. An agent must infer that this tool is for groups and the sibling is for individual users.

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