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

Beyond the annotations, it discloses real behavioral traits: committing 'freezes how it will be measured' (enabling before/after), dismissing records a reason 'so the pool learns,' and snoozing is temporary. It also states a crucial permission boundary — the tool 'cannot grant an agent permission to do anything; autonomy is set per brand in the product, never over the API' — which the destructiveHint=true annotation merely implies. The description is consistent with the annotations.

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 purpose and the three modes are front-loaded, followed by rationale and an explicit Args list mapping each parameter to its meaning. It is somewhat verbose relative to a 3-way enum decision, but each sentence adds behavioral or parameter value rather than padding.

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 6-parameter mutation tool with no output schema and low schema coverage, the description is largely sufficient: it covers the decision semantics, the consequence of each action, permissions, and five of six parameters. Return value format is not explained, but with no output schema that is less critical.

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 17%, so the description must carry the load, and it does for most parameters: it defines the action enum semantics, notes commit is the default, marks reason as recommended when action='dismiss', and gives snooze_days a default of 7. It omits user_intent, though the schema itself documents that field, so the gap is minor.

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 verb and resource: 'Decide on one suggestion: commit it, dismiss it, or snooze it,' and immediately enumerates the three decision modes. It also names list_opportunity_pool as the origin of the opportunity_id, letting an agent distinguish this tool from retrieval siblings like get_opportunities and list_opportunity_pool.

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?

It clearly explains when to use each action branch (committing creates tracked work, dismissing takes a reason, snoozing hides and returns) and cites list_opportunity_pool as the prerequisite source. It does not explicitly contrast itself with nearby mutating siblings like manage_action or manage_reddit_opportunity, so there is a small gap.

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