custom_rule

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

The description enumerates supported actions (create, update, delete, list, export, import), indicating behavior. However, it does not disclose side effects, permission requirements, or limitations like whether operations are reversible or batch constraints. With no annotations, the description carries the full burden but only partially satisfies it.

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?

The description is extremely concise: one sentence listing all core actions without any fluff. Every word contributes to the purpose, making it easy to parse quickly.

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 tool with 6 parameters, multiple actions, and no output schema, the description is too brief. It does not explain return values, how to construct the 'json' parameter for import, or how actions like 'list' behave. The agent lacks sufficient information to use the tool confidently.

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?

Input schema has 100% description coverage, so the baseline is 3. The description adds no extra meaning beyond what parameters already provide, such as parameter interdependencies or usage examples.

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?

Description clearly states the tool's primary actions: create, update, delete, or list custom rules. However, it does not differentiate from sibling tools like 'rules' which might manage similar resources, missing specificity about what makes these 'custom' 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?

No guidance on when to use this tool versus alternatives such as 'rules', 'setup', or 'knowledge'. The description lacks context about prerequisites, preferred usage patterns, or when not to use this tool.

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