Create Duplicate Rule

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

Annotations already indicate this is a write operation (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds prerequisites and the behavior of the rule itself, but doesn't disclose tool-specific behavior such as idempotency (despite idempotentHint=true) or what happens if the rule already exists. The description does not contradict annotations.

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?

Four sentences, each adding value: creation purpose, action modes, supported objects, and prerequisite. No redundancy or filler.

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 full schema coverage and no output schema, the description adequately covers the main purpose, dependencies, and rule behavior. It could additionally mention success/error responses, but that is not required given the schema richness.

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 100%, so the parameters are already fully documented. The description adds thematic context (e.g., actionOnInsert/actionOnUpdate map to block/warn/silent) and mentions the required matching rules, but doesn't elaborate on individual parameter syntax or edge cases beyond 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 tool 'Creates a Duplicate Rule' and explains its purpose (detect potential duplicates using Matching Rules). It also lists supported objects and the three action modes (block, warn, silent), which distinguishes it from sibling creation tools like sf_create_matching_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?

It provides clear context by stating that existing Matching Rules are required, implying the user must create those first. However, it doesn't explicitly name alternative tools or state when not to use this tool, so it's not fully explicit.

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