create_post

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

Discloses that it only drafts and does not auto-submit, which is important. However, no annotations provided, so missing details like authentication requirements, return value, or effect on state. Agent may need more on safety.

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 sentences, front-loaded with purpose. No redundant or irrelevant information.

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?

Adequate for a simple creation tool but lacks details on output (e.g., whether it returns a draft ID) and the need for manual submission. Could be slightly more complete given no output schema.

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 covers all 3 parameters with descriptions. The description adds minimal extra 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?

Clearly states 'Create a new post' with specific verb and resource. Differentiates from sibling tools which are all read-only or for other purposes. Also adds nuance about drafting, not auto-submitting.

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?

Implies usage for post creation but lacks explicit when-to-use or when-not-to-use compared to siblings. No alternatives mentioned, though context from sibling names helps distinguish.

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