Generate post preview URL

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that ('Reads account data', posts:read scope requirement), but omits what the tool actually returns (a URL) or whether it has side effects on the post.

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?

Three compact sentences with the core purpose front-loaded and no filler. It is efficient, though the fragment 'Reads account data' is slightly terse and could be integrated more meaningfully.

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 read-only tool with a fully documented 7-parameter schema and no output schema, the description covers the essentials but leaves gaps: it does not indicate that a preview URL is the return value, nor clarify the read-scope implications versus sibling preview tools.

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%, and each parameter — including the tier_ids/subscriber_id precedence rules and platform defaults — is already thoroughly documented in the schema. The description contributes no additional parameter meaning, so the baseline 3 applies.

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 ('Generate post preview URL') that is clearly distinct from siblings like get_post, send_post_test, and update_post. However, it does not explicitly contrast itself with send_post_test, which is the closest alternative for previewing a post.

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?

The description gives an authorization prerequisite ('OAuth integrations require posts:read') but never says when to use this tool versus alternatives like send_post_test or get_post. No when/when-not guidance is provided.

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