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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds nothing on top of that: no return format, no pagination, no auth requirements, no error behavior. With annotations in place the bar is lower, but zero added value still warrants a low score.

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?

It is a single short sentence with no padding, so nothing needs cutting. However, brevity here reflects under-specification rather than tight communication; the sentence is front-loaded but content-free.

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 one-parameter read tool with no output schema, the description should at minimum state what the view returns and what the identifier represents. Neither is present, and the reading basically duplicates the title, so an agent lacks enough to invoke it confidently over its close siblings.

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?

There is one required parameter, postId, and schema description coverage is 0%, so the schema supplies only a name and type. The description offers no clarification of what postId refers to, its expected format, or where an agent obtains it, leaving the only parameter undocumented in both places.

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 is a verbatim restatement of the title, 'Individual social post view page,' so it adds no distinguishing information beyond the name. It implies a read of a single post, but it does not say what the view returns or how it differs from siblings like social_posts_get, social_posts_list, or posts_rollup_social_posts_by_location. This is tautology-tier clarity.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. An agent cannot tell from this text why it would call posts_social_post_view rather than social_posts_get for a single post. Usage must be inferred entirely from the name and sibling list.

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