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

Annotations already declare this operation read-only, idempotent, and non-destructive, so the description need not restate those traits. It adds the resource qualifier 'static pages' but otherwise reveals no hidden behavior beyond what the annotations and schema already convey. There is no contradiction.

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 description is a single, tightly written sentence that front-loads the verb and resource and then lists the main capabilities. Every word contributes to the agent's understanding without filler or repetition.

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?

For a straightforward list operation, the one-line description plus a fully documented schema and an output schema cover the invocation needs well. It does not offer explicit tool-selection guidance relative to siblings, but that gap is more a usage-guideline concern. The 'static pages' qualifier provides enough resource context to make the description largely 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 description coverage is 100%, so all six parameters, including defaults, enums, and the blogId discovery hint, are fully documented in the schema. The description's phrase 'pagination, filtering, and sorting' aligns broadly with page/limit/order/orderBy/status but adds no meaning beyond the schema. 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?

The description opens with a specific verb and resource: 'List static pages.' It also names the key capabilities (pagination, filtering, sorting), and the plural 'pages' clearly distinguishes it from get_page's singular retrieval. The qualifier 'static' separates it from list_posts among the sibling 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?

The description gives no when-to-use guidance, exclusions, or alternatives. It does not tell the agent to use list_posts for posts or get_page for a single page, even though many list_* siblings exist. The only usage hint, 'Use list_blogs to discover available blog IDs,' is embedded in the schema rather than the tool description.

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