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 semantics are covered structurally. The description adds the action_type vocabulary (assign/regex_result/append_regex_result), which is genuinely useful behavior context since the schema leaves the nested object untyped, but it says nothing about permissions required or side effects on existing rules.

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, front-loaded with the operation and followed by the field list; nothing is padded. It is terse to the point that some items (meaning of 'field', target rule type) go unaddressed, but there is no wasted text.

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, and annotations cover the mutation profile. However, for a write tool in a family with both generic rules and rule_ticket variants, the description never clarifies which rule set rules_id refers to or what auth/scope is needed, leaving a meaningful ambiguity for an agent choosing among siblings.

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 only top-level parameter is a free-form 'input' object whose nested keys are the real payload. The description enumerates those keys (rules_id, action_type, field, value) and supplies the only enum-like vocabulary for action_type, which the schema does not provide. This compensates well for the schema's untyped additionalProperties, though the meaning of 'field' and 'value' is left unexplained.

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+resource ('Create a new action for a rule') and enumerates the fields involved, so the agent knows exactly what object is being created. It does not, however, distinguish this generic rule-action creator from the closely named siblings glpi_create_rule_criteria, glpi_create_rule_ticket or glpi_update_rule_action.

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 or when-not-to-use guidance, no prerequisites, and no pointer to alternatives such as glpi_create_rule_criteria or glpi_update_rule_action. The agent must infer that this is the write-side companion to glpi_list_rule_actions purely from the name.

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