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

Goes well beyond the annotations (destructiveHint, idempotentHint, openWorldHint=false) by disclosing the exact side effect: all scheduled posts are cancelled, quota is returned, reactivation does NOT restore them, and the count appears as canceled_posts in the response. This is precisely the destructive consequence an agent must surface before calling.

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 with the core action and its reversibility, then the cancellation consequence. Every sentence carries information, though the explanation of cancel semantics is repeated slightly ('CANCELS', 'cannot publish', 'cancelled', 'does NOT restore'), costing a bit of tightness.

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 compensates by naming the canceled_posts response field and the scheduled_posts pre-check field, so an agent knows both what it will get back and how to preview the impact. Complete for a one-parameter mutation tool.

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?

There is a single required parameter and the schema documents it at 100% coverage ('Account ID to deactivate'), so the description need not explain it. The description adds nothing about the parameter itself; its useful detail is about response fields, not inputs. 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?

States a specific verb and resource ('Deactivate a connected account') and immediately contrasts it against the other obvious lifecycle action by noting it 'stays connected so it can be activated again without reauthorizing', which separates it from chirpie_disconnect_account and chirpie_delete_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?

Gives a clear use context — stop publishing and free a plan slot while preserving the authorization — and points to chirpie_list_accounts' scheduled_posts as a way to preview the cost. It does not explicitly name disconnect_account or delete_post as the alternative when the user wants a full removal, so the exclusion is implied rather than stated.

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