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, covering the safety profile. The description adds no behavioral context beyond that — no mention of effects on existing rule evaluation, required permissions, or creation semantics. With annotations carrying the load, a 3 is the appropriate minimum-viable score.

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 the field list appended. No filler, though the field enumeration partially duplicates the schema description.

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 create tool whose safety profile is covered by annotations and which has an output schema, the description is minimally adequate. It nonetheless leaves gaps an agent would want: valid condition operators/values, and how criteria field names map to GLPI search options.

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's top-level 'input' object has additionalProperties={}, so inner fields are effectively undocumented by structure; the description's list of fields (rules_id, criteria, condition, pattern) is the main source of meaning. It still omits the accepted values for 'condition' or where 'criteria' field names come from (search options), so it does not fully compensate for the free-form nested object.

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 criteria for a rule'), which is inherently distinguishable from siblings like glpi_create_rule_action or glpi_create_rule_ticket. However, it never names or contrasts those siblings, and 'criteria' vs 'action' vs 'rule' selection is left to the agent's inference.

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?

The description offers no when-to-use guidance, no prerequisites (e.g., that the parent rule must already exist), and no mention of alternative tools such as glpi_create_rule_action or glpi_update_rule_action. Usage is only implicit in the name.

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