enable-rule

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

No annotations provided, so description carries full burden. It indicates a write operation (enable) and returns a confirmation. It also mentions prerequisite (rule exists) and suggests verifying name with list-rules. Lacks details on permissions or side effects, but for a simple toggle it's adequate.

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 clear, front-loaded sentences with no wasted words. Each sentence adds value: when to use, what to expect, what not to use.

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 one parameter, no annotations, but has output schema (not shown), the description covers purpose, return value, and prerequisite (rule existence). It suggests using list-rules for name confirmation. Fairly complete for a simple toggle tool.

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%. The description adds context that parameter 'name' is the exact rule name and recommends using list-rules to get it. However, it does not specify format, case sensitivity, or any constraints beyond the schema's minLength.

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 verb 'turning on' and resource 'existing Mail rule'. It distinguishes from siblings like disable-rule, create-rule, and delete-rule, providing specific purpose.

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?

Explicitly states when to use (turning on an existing rule by name) and when not to use, with specific alternative tools (disable-rule, create-rule, delete-rule). Also advises using list-rules to confirm exact name.

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