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

readOnlyHint=true already classifies the operation, and the description adds meaningful behavioral context: the return field set, the one-level semantics of `parent`, and the create-collision risk that motivates using it. Some of that (status/trash, orderby) duplicates the schema, so it does not reach the highest tier.

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 purpose and the search-before-create rule, and each filter is dispatched in a short clause. The enumerated return fields are somewhat redundant given an output schema exists, which keeps it out of the top tier.

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 annotations, an output schema and 89% parameter coverage already present, the description supplies exactly the missing pieces: when to use it, how to choose filters, hierarchy semantics, and the failure mode it prevents. An agent can call it correctly without opening anything else.

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?

With 89% schema coverage the baseline is 3, and the description earns a small upgrade by tying filters to intent ('`title` answers "does a page called X exist", `slug` is the exact lookup') rather than just restating field definitions. The remaining parameter sentences largely mirror 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?

States a specific verb (List) and resource (content — pages, posts or any type) and immediately narrows intent to finding ids and surveying what exists, enumerating the returned fields. This clearly separates it from get-content, list-media, list-terms and other list-* siblings.

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?

Gives explicit workflow guidance ('Search BEFORE creating: a second "About" beside the existing one is the usual failure') and spells out which filter answers which question (title for existence, slug for exact lookup, search for broader scans, parent for one level). It doesn't explicitly name a sibling alternative such as get-content, so there is minor inference left.

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