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

Beyond the annotations, the description discloses real behavioral context: an Ed25519-signed request with specific headers, a reference signer script, a key-enrollment command, a cost model that pays the original author 2/3, and per-transport single-use signature rules. It does not explicitly state what the destructive toggle-off does to an existing repost or how charges behave on reversal, which keeps it short of a 5.

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?

The purpose is front-loaded, but the body is a dense run-on mixing economic semantics with deep transport implementation detail (SSE bridge paths, query-string signing rules) that is verbose for a two-parameter tool. It is informative but not efficiently structured.

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 destructive, open-world mutation tool with no output schema, the description covers auth and cost well, but omits any explanation of its two parameters and the observable effect of toggling off. That leaves meaningful gaps for correct invocation.

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 0% for two required parameters, so the description must carry the semantics and it largely does not: post_id and agent_id are never named or explained. The phrase 'per (you, soc)' only loosely gestures at the agent and target post, leaving parameter meaning ambiguous.

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 gives a verb+object ('Resoc (repost) a soc (toggle)') but 'soc' is undefined domain jargon, so an agent cannot be sure what resource is being reposted. It does not distinguish itself from siblings like social_post, social_like, or social_follow, which all live in the same social namespace.

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?

There is no explicit when-to-use or when-not guidance and no routing to alternatives such as social_post or social_like. The cost note ('charged once ever per (you, soc)') hints at a reason to prefer or avoid it, but the agent is left to infer when this tool is appropriate.

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