Social Media Preview

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

No annotations are present, so the description carries the full burden of behavioral disclosure. The description only says 'shows preview' with no mention of side effects, permissions, rate limits, return format, or whether the operation is read-only. This lack of context is a significant gap for a tool with no structured annotations.

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 description is a single, compact sentence that is front-loaded with the action. It contains no redundant words or filler, making it highly concise and easy to parse. Every word contributes to conveying the core function.

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?

The tool has no output schema, so the description is responsible for explaining what the preview actually contains or returns. It merely states 'shows preview' without specifying whether the preview includes images, text, metadata, or how it is delivered. Given the low complexity (one parameter), some additional context about the return value is still necessary for an agent to understand the tool's behavior.

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 100% since the only parameter, postId, has a description ('Post/Page ID'). The tool description does not add any parameter-specific meaning, but according to the baseline for high schema coverage, a score of 3 is appropriate. No additional semantic value is provided beyond the schema.

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 clearly states the tool's function: it shows a preview for social media shares on Facebook, Twitter, and LinkedIn. The verb 'zeigt' (shows) and resource 'Vorschau für Social Media Shares' are specific, and this distinguishes it from sibling SEO tools like seo_analyze_content or seo_get_post_meta, which focus on analysis or metadata.

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?

No usage guidance is provided. The description does not indicate when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. The only hint is the tool name and basic function, which is insufficient for an agent to decide when to prefer it over other SEO or preview-related tools.

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