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

The description discloses critical behavior not covered by annotations: it returns a preview of changes and a confirmation link, and requires the merchant to confirm before changes are applied. This is essential context for a mutation tool with destructiveHint=false.

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 short sentences, front-loaded with the core action and then the important confirmation-flow caveat. Every sentence is necessary.

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 mutation tool with no output schema, the description covers the key behavioral aspect (confirmation flow). It is slightly incomplete regarding when to use it versus other blog post tools, but it is sufficient for correct invocation.

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 77%, so the schema already documents most parameters. The description adds a note that money is in integer minor units, but this parameter is not actually present in the schema, making it irrelevant to this tool's parameters. The description does not add meaningful detail beyond schema coverage.

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 ('Change a blog post') that clearly distinguishes it from blog_posts_create, blog_posts_delete, and blog_posts_set_status.

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 clarifies the two-step confirmation flow (preview then merchant confirmation), which sets it apart from the other CRUD tools. However, it does not explicitly say when to use this tool versus blog_posts_create or set_status.

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