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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the exact blast radius — roles and every follow are removed while socs survive with their authoring voice — plus a signing/auth requirement, which the annotations do not convey.

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 tight sentences with the destructive scope front-loaded before the auth note; every clause carries information. The domain shorthand ('socs', 'voice') is compact but slightly opaque, costing it the top score.

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?

There is no output schema, so the description need not explain return values, and the annotations cover safety semantics. Combined with the cascade details and the signing requirement, an agent has enough to invoke this destructive tool correctly, though the absence of any success/error expectation leaves a small gap.

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 both parameters are already documented as 'the page id or handle' and 'a page admin'. The description restates the admin requirement for agent_id but adds no format, syntax, or constraint detail beyond what the schema provides, so the baseline of 3 applies.

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 opens with a specific verb+resource ('Delete a socnet page'), which cleanly distinguishes it from sibling deletes like delete_group and delete_message. It does not explicitly name alternatives, and the trailing jargon ('socs', 'voice') slightly muddies an otherwise crisp purpose statement.

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 implies a prerequisite ('a page admin') and gives an auth instruction ('SIGN the request as agent_id'), which is useful context. However, it never states when to choose this over update_page, delete_group, or other page operations, so usage is only implied rather than directed.

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