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 non-structured behavior: ordering ('newest change first') and pagination limits ('20 a page, up to 100'), which the annotations do not convey. Returned fields are also enumerated, though pagination cursor mechanics less so.

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-loaded with the core action, then platform coverage, returned fields, filters and pagination in a tight sequence. It is dense with almost no filler, though the WordPress/Shopify type enumeration is somewhat list-heavy and could be compressed.

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 usefully enumerates the returned fields (id, title, status, address, change time, alt text) and covers filters and paging, which is most of what an agent needs. The gap is that media_type's role and the meaning of the page cursor are left to the schema.

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 57%, so baseline is 3. The description compensates somewhat by defining search as words, listing status values, and giving the per_page default/max ('20 a page, up to 100'), but it partially duplicates the schema's type and status text and never explains media_type (image/video/audio/application), leaving one enum-gated 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?

States a specific verb ('List') and resource ('content of a connected site') and immediately scopes it by platform (WordPress vs Shopify content types), which cleanly separates it from siblings like content_get, content_save, content_upload and content_trash. An agent can identify this as the enumeration tool without opening the schema.

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?

It gives implied usage through filters ('Filter with search (words) and status') and default types per platform, but never names an alternative or states when not to use this tool (e.g., versus content_get for a single item). The agent must infer the listing-vs-fetch boundary from sibling names alone.

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