upsert_post_from_payload

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

With no annotations provided, the description must disclose behavior itself. 'Create or update' signals mutation but nothing about dry-run semantics, publishing/scheduling side effects, overwrite behavior, idempotency, or required permissions. The description is not misleading, but it is far too minimal.

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?

The description is a single efficient sentence with no filler and no redundant restatement of the tool name. It is concise, though its brevity comes at the cost of substance.

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?

This is a mutation tool with four parameters, two enums, no annotations, and no output schema, yet the description says almost nothing about behavior, modes, target selection, or expected effects. An agent would not be able to call this tool reliably based on the provided description alone.

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%, and the description provides no parameter-level explanation. It does not clarify payload_path, mode, intended_mode, or explicit_target_id, leaving the agent to guess the meaning and interaction of these parameters.

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 the tool creates or updates a WordPress post from a payload JSON file, using a specific verb and resource. It is understandable on its own but does not explicitly distinguish itself from siblings like upload_media, publish_now, or upsert_share_block.

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?

There is no guidance about when to use this tool versus alternatives. The phrase 'from an existing payload JSON file' implies a narrow use case, but no explicit conditions, exclusions, or preferred alternatives are given.

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