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

Annotations already mark destructiveHint=true and idempotentHint=true. The description adds meaningful behavioral context beyond that: the deletion is scoped to rules only, not explicit registrations, and an Enterprise account is required. This supplements the annotations without contradicting them.

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 three short sentences, with the primary action front-loaded. Every sentence adds value: the action, the id source, the exclusion scope, and the authentication requirement. There is no 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 single-parameter, destructive tool with full parameter schema, annotations, and an output schema, the description covers all essential operational details: what is deleted, how the id is obtained, what is not affected, and the required account level. Nothing an agent needs to call it correctly is missing.

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 100%, and the schema already specifies the id as 'Rule id, from jt_watch_rules_list.' The description restates this id source but does not add significant new parameter semantics beyond the schema, so the baseline of 3 applies.

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 states a specific verb and resource: 'Delete a watch-by-profile rule by id'. It also differentiates from siblings by explicitly noting it does not touch explicit registrations from jt_watch_set/jt_watch_add, so an agent can distinguish this from watch_remove without opening the schema.

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 includes a clear when-not condition ('Does not touch explicit registrations from jt_watch_set/jt_watch_add'), a prerequisite ('Requires an account key (Enterprise)'), and the source of valid ids (jt_watch_rules_list). This gives the agent enough context to decide when to use this tool over the watch removal siblings.

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