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

Annotations already cover destructiveness, idempotency, and closed-world scope, so the bar is lower. The description still earns credit by disclosing the non-obvious side effect that the account is also removed from associated media kits, plus the caller-type authorization rule for agency callers.

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 sentences, front-loaded with the destructive effect and the media-kit cascade before the selection mechanics. Dense but every clause carries information; minor loss for cramming three constraints into one long first sentence.

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?

Covers the target selection modes, the caller-dependent creator_id requirement, and the cascading media-kit effect; an output schema exists so return values need not be explained. Nothing an agent needs to invoke it correctly appears to be missing, though permission/auth details beyond 'agency callers' are not expanded.

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 coverage is 100%, so baseline is 3. The description goes beyond the schema by framing social_id vs platform+handle_or_url as alternative selection strategies and by stating the agency-only requirement for creator_id, not just repeating field definitions.

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?

Names a specific verb and resource (remove a linked social account from the authenticated creator or an agency roster creator) and adds the cascade to associated media kits. An agent can distinguish this from social_add and social_list without opening either schema.

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?

Specifies how to select the target (by social_id, or by platform with optional handle_or_url) and states the agency precondition that creator_id is required. It gives clear context but does not contrast itself against siblings such as social_list or social_add, nor state when removal is inappropriate.

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