Create Rule

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

The annotations indicate this is a write operation (readOnlyHint=false) but not destructive. The description adds no extra behavioral context beyond 'Create', such as side effects, authorization needs, or implications for existing rules.

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 a single sentence and thus concise, but it omits critical details that could be added without compromising conciseness. It is appropriately front-loaded but insufficiently informative.

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?

Given the tool's complexity (7 parameters, nested objects for conditions and notifications), the one-sentence description is woefully inadequate. It fails to explain what a rule is, how conditions work, or what the output schema returns, relying entirely on the structured schema.

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?

With schema description coverage at 57%, the description should compensate for undocumented parameters, but it adds no information about parameters at all. The meaning of 'conditions', 'notification', etc., is left entirely to the schema.

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 clearly states the action 'Create a new rule' and the context 'Connhex Rules Engine'. It is unambiguous about the tool's purpose and distinguishes it from siblings like delete_rule or update_rule, but it doesn't differentiate from other 'create' tools like create_resource.

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 provides no guidance on when to use this tool versus alternatives (e.g., creating other resource types). There is no mention of prerequisites, conditions for use, or when not to use it.

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