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

Annotations already declare destructiveHint=true, readOnlyHint=false and non-idempotent, so the safety profile is covered by structured data. The description adds the semantic of what a trigger is and examples, but says nothing about what removal destroys (existing matches, scan history), permissions, or duplicate-keyword behavior, which is the context annotations don't supply.

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?

Front-loaded purpose sentence, then a compact definition of triggers, then a clean Args block. Every line earns its place; the example trigger list is useful rather than 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?

With no output schema, the description covers purpose, trigger semantics and all action-relevant parameters, and annotations cover mutation safety. It is slightly thin on the consequences of removal and on error/duplicate handling, but an agent has enough to call it correctly.

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 only 20%, so the description carries the burden and does so for 4 of 5 params, including the conditional requirement logic (keyword for add, trigger_id for remove) that the schema itself does not express. Only user_intent is unexplained here, though it is described in the schema.

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 pair (add/remove) and resource (keyword trigger) and even explains the concept: 'the strings the scan looks for inside posts and comments.' It implicitly separates itself from manage_reddit_subreddit and manage_reddit_opportunity by resource, but never names a sibling, so it stops short of the top band.

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 per-action requirements ('keyword: Required for add', 'trigger_id: Required for remove') give conditional usage guidance, which is genuinely useful. However there is no statement of when to prefer this over scan_reddit or the other Reddit management tools, and no exclusions or prerequisites.

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