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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered without the description. The description adds little beyond that, though 'null if not parseable' for content_blocks is genuine behavioral context about a partial-failure case.

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, followed by a compact return summary and a short args list. The return-value sentence is somewhat redundant given an output schema exists, but overall the text is tight and wastes little.

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?

Since an output schema exists, the return-value detail is a bonus rather than a requirement, and the description covers both required params and the nullable-block edge case. Missing only error behavior for a nonexistent or inaccessible post, which is minor for a read tool.

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 coverage is 0% (both params are bare 'Post Id'/'Project Id' strings), so the description must compensate. It gives post_id real format guidance ('UUID from list response, or full SK like cms-post-data-<uuid>'), which is meaningful; project_id gets only a tautological gloss.

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 ('Get a single CMS blog post's content') and specifies the retrieval mode ('as HTML and as blocks'), which distinguishes it from list_cms_posts and the create/update/delete CMS siblings. It stops short of naming the sibling to use for batch retrieval, so it is clear but not fully differentiated.

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?

Usage is only implied: 'single' implies the alternative to list_cms_posts, and the post_id hint ('UUID from list response') hints at the list-then-get workflow. There is no explicit when-to-use/when-not statement or named alternative.

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