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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true and idempotentHint=false, so the mutation and safety profile is covered. The description adds nothing beyond that: no mention of required permissions, whether duplicate problems are rejected, or what the operation returns.

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 short sentences with the purpose front-loaded and field hints second. Tight and efficient, though the field list is a bare enumeration with no indication of which fields are required.

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?

An output schema exists, so return values need not be explained. For a create tool whose input is an unconstrained object, however, the description gives only four sample fields and no required/optional distinction, leaving the agent under-specified on the actual payload.

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 schema exposes only a free-form "input" object (additionalProperties: {}), so the enumerated fields (name, content, entities_id, users_id_requester) provide real semantic value that the schema does not. It falls short of a full field list or required-field indication, hence not 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?

States a specific verb and resource ("Create a new problem"), which is unambiguous on its own. However, it offers no differentiation from the many sibling create tools (glpi_create_ticket, glpi_create_change, glpi_create_asset), leaving the agent to infer from the name alone when a problem is the right ITIL object.

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 prerequisite information, and no mention of alternatives such as creating a ticket or change. Nothing tells the agent under what circumstances a problem record should be created rather than another ITIL type.

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