Create Post

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

Annotations are non-committal (readOnlyHint=false, destructiveHint=false). Description adds meaningful behavioral details: Notion page creation, WordPress sync, and markdown requirement, going beyond structured annotations.

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?

Two concise sentences without fluff. Front-loaded with main verb and resource.

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?

No output schema and description does not mention return values. For an 8-parameter creation tool, this minor gap makes it adequate but not fully 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 description adds minimal value beyond the schema. It reinforces markdown and publish behavior but duplicates schema info.

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?

Clearly states the tool creates a new blog post, involving Notion page creation and WordPress sync. This distinguishes it from siblings like update_post or 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?

Provides basic context (create post, markdown body, publish draft) but does not explicitly contrast with sibling tools or indicate when to use alternatives like direct_publish.

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