create_post

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

Description mentions defaults (dry_run, private) but lacks disclosure of side effects when dry_run is false (actual posting), authentication needs, rate limits, or error behavior. With no annotations provided, the description carries full burden and is insufficient.

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?

Very short (two sentences) and front-loaded, conveying essential defaults. However, it prioritizes brevity over completeness; additional structured information would fit without being verbose.

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?

Given the complexity (7 parameters, no annotations, no schema descriptions, but an output schema exists), the description omits return value info, parameter details, and behavioral context. It is not complete enough for an agent to use reliably.

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 0% (no parameter descriptions). Description only covers two defaults (dry_run, security) out of seven parameters, leaving body, subject, journal, tags, posted_at unexplained. This does not compensate for the lack of schema documentation.

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?

Description clearly states 'Post a new entry to your LiveJournal journal', specifying the verb and resource. It distinguishes itself from sibling tools, which are mostly reading or caching, but could be more explicit about being a write operation.

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?

No guidance on when to use this tool versus alternatives. The sibling tools are all read/cache oriented, so usage is implied but not stated. No when-not-to-use or context for selection.

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