Resume Community Member Subscription

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so mutation and openness are known. The description usefully adds that it 'changes community state' and that confirm=true is required, but it never says what is actually resumed or what side effects (billing, notifications) occur.

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?

Two short sentences with the mutation warning and confirm gate front-loaded and no filler. It is efficient, though the first sentence is largely wasted on restating the title.

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 1-required-param mutation with rich annotations and no output schema, the essentials (mutating, confirm gate) are covered. The main gap is the absence of any when-to-use context relative to cancel/archive siblings.

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 100%, so subscription_id, account, and confirm are already documented in the schema. The description echoes the confirm requirement but adds no format, constraint, or usage nuance beyond the schema text.

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 first sentence 'Resume Community Member Subscription' restates the tool name/title rather than explaining what resuming a subscription entails. The verb+resource are recoverable, but there is no differentiation from the sibling cancel_community_member_subscription or any hint about what state changes.

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 states a prerequisite ('requires confirm=true') but gives no when-to-use guidance and names no alternative. An agent learning only from this text cannot tell when resume is appropriate versus cancel or archive.

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