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

Discloses important side effects beyond annotations: it creates a Notion page, triggers sync to WordPress, and supports draft vs immediate publication. This adds real behavioral context that readOnlyHint/destructiveHint cannot capture.

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?

Short, direct sentences with the core action and key behavioral facts front-loaded. No filler or redundancy.

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?

The description covers the core workflow, side effects, and draft/publish behavior, while the output schema and fully documented input schema supply the remaining details. Nothing critical is missing 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 100%, so the baseline is 3. The description reiterates the markdown body and publish semantics already present in the schema without adding new parameter-level detail.

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 action ('Create a new blog post') with concrete side effects (creates a Notion page and triggers sync to WordPress). The word 'new' and the draft/publish distinction separate it from update_post, publish_post, and direct_publish.

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?

Gives clear context for using publish=true vs false, but does not explicitly state when to prefer sibling tools like direct_publish or publish_post. The creation-focused wording implies usage, but alternatives are not named or excluded.

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