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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered elsewhere. The description adds nothing beyond that – no note on whether the rule is fetched live, what happens for unknown/invalid IDs, or any permission/auth context.

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?

A single front-loaded sentence with the purpose and the key lookup key ('by ID') first; no filler or redundancy. It is appropriately sized, though extremely terse, leaving room that guidance could have used.

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 and full annotations exist, so return values and safety need not be repeated. For a simple single-item getter the description is minimally sufficient, but it omits when-to-use routing against the rule-related siblings, which is the one thing structured fields cannot supply.

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 fields, format, ruleId and expand_dropdowns are already documented in the schema with enums and patterns. The description mentions only 'by ID' and adds no semantics beyond the schema, so the baseline 3 applies.

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 ('Retrieve a ticket business rule (RuleTicket) by ID'), naming the GLPI entity so an agent knows what object is returned. It does not, however, distinguish itself from nearby siblings such as glpi_list_rules or glpi_list_rule_ticket_criteria other than by implying single-item retrieval.

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 only usage cue is 'by ID', with no statement of when to use this versus the rule-listing tools or the criteria/action siblings. There are no prerequisites, exclusions, or alternatives named, so the routing decision is left entirely to inference.

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