next_discovery_tip

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

No annotations provided, so the description fully bears the burden. It discloses key behaviors: respecting off/snooze/power-user settings, frequency cap (≤1 per 20 min, ≤3 per day), recording to avoid repeats, and returning '' when no tip. This is comprehensive for a discovery tool.

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 two paragraphs, with the first sentence succinctly stating the core purpose. It efficiently conveys additional details without unnecessary fluff, though slightly longer due to behavioral clarifications.

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 the tool's complexity (behavioral rules, frequency caps, recording), the description covers all necessary details for correct invocation. Since an output schema exists, the return value format is likely documented elsewhere, and the description sufficiently explains when to expect results.

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 has no description for the sole parameter 'context' (coverage 0%). The description adds crucial semantics: 'Pass context as comma-separated trigger tags.' This clarifies the expected format and purpose beyond the schema definition.

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 returns 'ONE earned, not-yet-shown feature tip' or empty string. It uses a specific verb ('return') and resource ('feature tip'), and differentiates from sibling tools like discovery_intro and discovery_status by focusing on earned discovery.

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 explicitly lists trigger moments (e.g., 'user starts a project, writes R code'). It does not explicitly mention when not to use or compare to alternatives, but the trigger list provides clear usage context.

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