set_discovery_tips

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

The description explains the meaning of each parameter, which adds transparency. However, without annotations, it fails to disclose whether this is a safe or destructive action, any side effects, or authorization requirements.

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 brief and structured, with a clear purpose statement followed by parameter explanations. Each sentence serves a purpose, and it is front-loaded. It is appropriately sized for a simple configuration tool.

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 preference-setting tool with three parameters, the description adequately covers the tool's purpose and parameter semantics. The presence of an output schema reduces the need to describe return values. It does not mention edge cases but is sufficiently complete for correct usage.

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?

The schema has no parameter descriptions, so the description compensates by explaining each parameter's function. It clarifies that enabled turns tips on/off, power_user sets mode, and snooze_days snoozes for N days. This adds significant meaning beyond the raw schema, though it could be more precise about ranges.

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 adjusts feature-tips preference, using a specific verb and resource. It distinguishes from sibling tools like next_discovery_tip (show tip) and discovery_status (get status). However, it could be more explicit about the scope.

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 usage guidance. It does not explain when to use this tool versus alternatives like next_discovery_tip or discovery_status, nor does it mention prerequisites or exclusions.

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