mnemosyne_pheme_watch

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

There are no annotations, so the description carries the full burden, and it does so richly. It discloses ownership semantics ('The lists are THEIRS'), failure behavior ('an op that would empty a list is refused'), per-op outcomes, receipt side effects, the prerequisite that the app must be running, and the guarantee that nothing posts anywhere.

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 longer than average but dense: every clause earns its place by adding a distinct behavioral fact. It front-loads the primary action before providing usage, exclusions, and side effects. Minor splitting of the first long sentence would improve readability, but it is not bloated.

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?

With no annotations and no output schema, the description fully compensates: it covers what the tool does, when to use it, what it deliberately does not do, failure modes, per-operation reporting, receipt behavior, and runtime prerequisites. An agent has enough context to invoke it correctly and anticipate consequences.

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 already describes all parameters: ops array, op enum, kind enum with meaning, and value max length. The description adds useful context about how these operations behave, but it does not substantially change or extend parameter meaning beyond the schema's 100% coverage.

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 operation and resource: 'Put a subreddit, a Hacker News search query or a topic on the human's Pheme radar ... or take one off.' It clearly distinguishes what the tool does from siblings by adding 'It does not scan and it does not post.'

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 names when to use the tool with a concrete example: 'Use it when a conversation has found a community worth watching.' It also states non-uses ('It does not scan and it does not post'), though it does not explicitly name an alternative tool such as mnemosyne_pheme_radar for viewing the radar.

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