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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=true. The description usefully adds that toggling off does not delete the message, which directly answers the question the destructiveHint raises. There is mild tension with destructiveHint=true, but a state toggle is not a hard contradiction of that hint.

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?

Two short sentences with zero waste. The core action and the flag mapping are front-loaded, and the non-destructive reassurance follows immediately.

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 simple toggle, annotations cover the safety profile and the schema covers all parameters, so the description is nearly sufficient. The garbled welcomeId schema text ('Delete and enrollExisting.') is a schema problem rather than a description gap.

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 schema already documents all three parameters, including active's on/off meaning. The description's restatement of active:true/false adds no meaning beyond the schema, so baseline 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?

States a specific verb+resource ('turn a welcome message on/off') and clarifies the toggle semantics with the active flag. 'Nothing is deleted' implicitly distinguishes it from delete_welcome_message, but it never explicitly differentiates from close siblings like update_welcome_message.

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 when-to-use guidance, prerequisites, or named alternatives. With siblings such as update_welcome_message, delete_welcome_message, and list_welcome_messages present, the agent gets no explicit routing signal for choosing this tool.

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