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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral/data context – that `brief` is null until upsert_post writes it, and that `serpBrief`/`customInstructions` are paid SERP research distinct from `brief` – but says nothing about errors (e.g. missing id) or the read's scope.

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-loads the core action well with 'Get one post by id.' However, the middle sentences about brief/serpBrief/customInstructions are tangled and partly redundant ('separate from `brief`, the editorial plan' re-explains `brief`), making them harder to parse than they need to be.

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?

With no output schema, field semantics are valuable, and the description does explain several returned fields. But it explains only a subset, gives no guidance on the `id` parameter, and omits any concurrency/error behavior, so a get-by-id tool remains only partially specified.

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 50%: workspaceId is documented in the schema, while the required `id` is undocumented. The description, however, spends its words on return fields (brief, serpBrief, customInstructions, standard) and adds no semantics for either parameter, so it fails to compensate for the gap on `id`.

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 and resource: 'Get one post by id.' Naturally distinguishable from list_posts (single vs many), but it never names or explicitly contrasts with any sibling, so the differentiation is left implicit.

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 or when-not-to-use guidance. The mention of upsert_post is only a note about when `brief` becomes non-null, not routing advice for choosing this tool over list_posts or get_profile. Usage must be inferred from the tool name alone.

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