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

Annotations already declare readOnly/idempotent/non-destructive, so the safety burden is covered; the description adds genuine value beyond that by disclosing the returned fields (id, slug, full content JSON, visibility, timestamps) and the paging mechanism. It still doesn't mention pagination limits or total counts, but that is a minor gap.

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: scope first, filters second, return shape third, alternative-tool note last. No redundancy and nothing before the key filtering constraint.

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 compensates by naming returned fields, and annotations cover the safety profile, leaving an agent able to call it correctly. Only pagination behavior/limits remain unaddressed.

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 0%, so the description must carry the load; it does define content_type as a slug filter and enumerates visibility values, but the visibility default is already in the schema and it never explains site_id or the limit/offset semantics (default 50, max 200) beyond the word 'paging'.

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 ('List content items') with concrete examples (blog posts, projects) and the scoping key (site + content_type slug), which cleanly separates it from siblings like list_content_types or list_sites.

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?

Explicitly routes mutation intent to add_content_item / edit_content_item / delete_content_item, so the agent knows this is the read path. However, it gives no guidance on when to prefer this over other listing/read tools (e.g. list_content_types, get_site_tree) or prerequisites for the content_type slug.

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