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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds real value by clarifying that content is 'the stored source' (raw, editor-view) and listing platform-specific return fields, which goes beyond what the annotations provide.

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?

Core purpose is front-loaded in the first clause, and the following platform detail is informative rather than filler. The WordPress/Shopify field enumeration is somewhat long but earns its place by telling the agent what to expect.

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, the description carries the return-value burden and does so thoroughly, listing the fields per platform and clarifying the raw-source nature of content. Minor gaps remain: what 'id' refers to and how ids are obtained, but the tool is otherwise complete.

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%; the site parameter is well documented and references connected_sites, but the required 'id' has no description and 'type' is only 'Default post.' The description provides no parameter-level guidance to compensate, so 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 ('read') and resource ('one item of a connected site'), and immediately scopes it against the sibling list-style tool by emphasizing a single item read 'in full'. It enumerates the returned fields per platform, so an agent knows exactly what this retrieves versus content_list.

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 single-item framing implies usage versus content_list, but there is no explicit when-to-use/when-not statement or named alternative. The agent must infer the routing from the resource scope rather than being told.

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