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

Annotations already declare this a safe, idempotent, closed-world read, and the description goes well beyond that: entry ids are the article ids used by other plan/article tools, shadowExistingContent behavior depends on list_existing_pages, and when existingContent.enabled is set the plan never schedules covered ideas, with skippedCovered exposing coveredBy plus refresh suggestions. This is exactly the extra causal/semantic context annotations cannot 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?

The purpose is front-loaded in the first clause, followed by filtering mechanics and then the more intricate existing-content behavior. It is dense and long, but nearly every sentence carries real semantic payload about the plan's return contents; the main cost is readability of the unbroken block.

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 and a five-parameter, domain-heavy read, the description carries most of the burden and does well, explaining what the payload contains and how skippedCovered/coveredBy are shaped. It leaves minor gaps: overdueOnly's meaning and limit/offset defaults are not restated, and site is undocumented beyond its single-value enum.

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 60%: status and overdueOnly are documented in the schema while limit/offset are not, and the description fills that gap ('page with limit/offset'). However the schema already defines status's enum values, and the description does not explain the site parameter or defaults/ranges, so it adds only partial value over the structured fields. Baseline 3 is appropriate.

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 ('Read the site's content plan') and enumerates exactly what the plan contains: entries, suggested topics, settings, runway, trial limits. It also cross-references list_existing_pages, which helps an agent separate this tool from the many sibling read tools.

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?

'Call this first before changing the plan' gives a clear ordering rule and implies this is the prerequisite read before mutating tools like update_plan_entry or add_to_plan. It does not, however, name which sibling to use instead for adjacent needs (e.g., list_articles for raw articles), so the guidance is clear but not exhaustive.

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