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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds genuinely new behavioral context: passing `as` meters consumption with a per-entry fee split to authors, while omitting it is free browsing. It also discloses the structural caveat that the timeline excludes replies. It stops short of return-shape or pagination behavior, but no output schema exists and the additions clearly exceed annotation coverage.

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 mode enumeration before caveats, and every sentence carries routing or cost information. The all-caps reply warning is echoed again inside the post_id schema description, so it is stated twice across the definition, which is mild redundancy rather than waste.

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 6-parameter, zero-required read tool with no output schema, the description covers all access modes, the free/metered trade-off, and the reply-location trap that would otherwise cause wasted calls. Only the absence of any guidance on limit/pagination 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 67% and the schema already documents as/author/post_id, so the heavy lifting is done there. The description adds the negative semantics the schema lacks ('omit as to browse free') and frames the modes as mutually selecting alternatives, which aids parameter choice.

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 precise verb and resource ('Read SOCNET') and enumerates the exact access modes: single soc by post_id, timeline, tag, author, or Following. An agent can distinguish this from social_post/social_resoc/social_like purely from the description.

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?

Explicitly tells the agent when to use post_id versus scanning: 'when a notification says someone replied to your soc, call this with its post_id rather than scanning the feed.' It also states the free-vs-metered choice condition for `as`, which is an operational routing decision.

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