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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds one useful piece of return context: the response includes the `seliee_rules` payload. It says nothing about behavior when the rule is not found or when both identifiers are passed.

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 action, resource, identifier options, and returned payload. Nothing wasted.

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 no output schema, the description mentions the `seliee_rules` payload but gives no sense of the returned structure. Given two optional identifiers and no documented behavior for the neither-provided case, an agent lacks some information needed to call this reliably.

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 0%, so the description must carry the load; it does identify both parameter names and frames them as alternatives. However, it does not say which takes precedence if both are given, nor that at least one is effectively required despite the schema marking neither as required.

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 (fetch) and resource (a single seliee_rule), and the word 'single' implicitly distinguishes it from the sibling list_rules. It also names the payload it returns. It stops short of explicitly contrasting with get_rule_variables or list_rules.

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 phrase 'by `rule_id` or `rule_uuid`' implies two mutually exclusive lookup paths, which is mild usage guidance. There is no statement of when to prefer this over list_rules or get_rule_variables, and no note on what happens if neither identifier is supplied (both are optional in the schema).

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