Prepend content to an existing esa post

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

Description adds behavioral context: no need to fetch current body, same as append but at start, optionally set wip. Annotations already indicate destructiveHint=true, which aligns with the operation. No contradiction.

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 well-structured sentences, front-loaded with purpose. No unnecessary details; every sentence adds value.

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 tool's complexity (5 params, no output schema), the description covers action, siblings, parameter tips, and prerequisite (teamName via esa_get_teams). Complete for agent selection and 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 description coverage is 100%, but the description adds extra semantics for 'content' parameter (4 spaces indentation, LF normalization, blank line for block) and clarifies defaults for 'wip' and 'message'. Provides value beyond schema.

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?

The description clearly states it prepends Markdown content to an existing post's body as a new revision. It distinguishes itself from esa_update_post (no need to fetch body) and esa_append_post (prepend vs append).

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 explains when to use it over esa_update_post and esa_append_post. It does not explicitly state when not to use it, but the context is clear.

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