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

Annotations already declare readOnly/idempotent/non-destructive, so the description focuses on data semantics: slots live as `seliee_rule_<slot>` and hold newline-separated text lists, and the return is a field name plus an example value. That is real context beyond the annotations. It doesn't say what happens for an unknown slot key, keeping it from a 5.

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?

Three sentences, reasonably front-loaded and free of filler. But the lead sentence is hard to parse on first read, and the storage-format detail is interleaved in a way that delays the actual calling guidance.

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?

There is no output schema, so the description must define the return; it partially does (field name + example value for a specific slot) but never specifies the shape or keys of the 'every slot' response, which is exactly what an agent calling without a key would need.

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 coverage is 0%, so the description carries the burden and does explain the parameter's two modes with example key values. But there is a naming mismatch – the schema field is `seliee_rule_key`, which reads like a rule identifier, while the description says to pass a 'slot key' – and no format constraints are given, leaving avoidable ambiguity.

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?

The description states the specific resource – the slot variables ('seliee_rules' map keys) a rule accepts – and gives concrete slot examples (`ip_white`, `agent_block`). The opening clause 'Slots a seliee_rule's `seliee_rules` map accepts' is grammatically awkward, and it does not distinguish itself from the many sibling *_variables tools (get_image_variables, get_template_variables, get_website_variables), but the resource is identifiable.

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?

It gives per-parameter guidance ('pass a slot key for its field name and example value; without a key, returns every slot'), which implies two calling modes. However, it never says when to reach for this tool versus get_rule, list_rules, or edit_rule in the rule-authoring workflow, so the agent must infer its role.

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