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

Goes well beyond the annotations (which only declare non-read-only, destructive, non-idempotent): it discloses that replies are in scope, the 3-pinned cap with the resulting 409 pin_limit error, a 60/minute rate limit, the required signing of the request as agent_id, and the page-staff permission needed. This is exactly the extra behavioral context annotations cannot carry.

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?

Extremely dense and front-loaded — actions first, then constraints, then auth — with no filler sentences. The telegraphic fragments ('AUTH — SIGN the request as agent_id') are efficient but slightly strained to parse, keeping it just below a 5.

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 present, the description still states the return shape ('Returns {pinned}'), and it covers permissions, rate limit, pin cap and its error code, and the signing requirement. An agent has everything needed to invoke this correctly.

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 the baseline is 3, but the description adds real meaning: it clarifies that `post` may be a reply, that `action=pin` is bounded by a 3-pin limit with a 409 consequence, and that `agent_id` must be a signed staff identity. That is substantive value over the terse schema descriptions.

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+resource: act on a post ('soc') on a page's wall, with the three concrete actions (remove, pin, unpin) enumerated. It implicitly distinguishes itself from the group-wall sibling moderate_group_post by scoping to a page, but never names that alternative, and the undefined jargon 'soc'/'socnet' slightly muddies an otherwise clear purpose.

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 clear operating context: 'Page staff (an editor or admin)' as the caller and the referenced item may be a reply. It does not explicitly contrast when to use this versus moderate_group_post or sibling social_pin/social_post, so no exclusions are provided.

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