Activate Bounce

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

The description adds context beyond annotations by noting the tool is blocked in read-only mode and by clarifying that it reactivates a deactivated address tied to a bounce. This complements the readOnlyHint=false annotation without contradicting it.

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 a single sentence plus a short operational note. Every word contributes to understanding the purpose and a key constraint, with no redundancy.

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 one-parameter tool with an output schema, the description is complete enough: it states the action, the target resource, and an important operational limitation. The output schema covers return values, so those do not need description.

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 single parameter bounce_id is fully described in the schema as 'Numeric bounce ID to reactivate.' The description adds no additional semantic context about the parameter, so with 100% schema coverage, baseline 3 is appropriate.

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?

Description uses a specific verb 'reactivate' and clearly identifies the resource: a deactivated address tied to a bounce. This distinguishes it from sibling tools like list_bounces or get_bounce, which are read operations.

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 implies use when an address tied to a bounce needs to be reactivated, but it does not explicitly state when to use this tool versus alternatives or give exclusions beyond the read-only mode block. The 'BLOCKED in read-only mode' note provides some context but not full guidance.

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