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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is partly covered. The description adds that it returns seliee_rule_id and seliee_rule_uuid, but does not explain what the destructive behavior affects, required permissions, or failure modes.

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 short sentences with the action front-loaded and return values stated directly. There is no unnecessary 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?

For a creation tool with a nested object parameter, 0% schema description coverage, and no output schema, the description leaves key details undocumented: the shape of seliee_rules and the purpose of seliee_rule_title. It partially compensates by naming the returned IDs, but not enough for correct invocation.

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%, and the description mentions only the seliee_rules payload while saying nothing about seliee_rule_title or the expected structure of the nested seliee_rules object. This is insufficient compensation for the undocumented parameters.

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: creating a new seliee_rule from a seliee_rules payload, and mentions the returned identifiers. It does not differentiate itself from siblings such as edit_rule, get_rule, or delete_rule.

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 implies creation but gives no explicit guidance on when to use this tool versus edit_rule, get_rule, or other create_* tools. It also omits prerequisites or when-not-to-use conditions.

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