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

Goes well beyond the annotations: it discloses that the write is gated on human approval through Royally and that nothing changes until then, that content is stored verbatim as post_content, and that the connection cannot reverse the change. Those are exactly the operational facts an agent needs before committing a write.

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?

Front-loaded with what gets created, then the Elementor exclusion, then the approval/irreversibility caveats. The two closing sentences about Royally overlap slightly in restating irreversibility, but every sentence carries distinct 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?

For a 15-parameter write tool with no output schema, the description covers the key risks (approval gate, no undo, verbatim content storage) and the main alternative. It does not indicate what is returned (e.g., the new post ID) or what happens on slug collisions, which would be the remaining gaps.

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 coverage is 73%, so most parameters are already documented, and the description mainly groups them narratively ('taxonomy terms, custom-field meta, and a featured image, in one call'). It adds the useful 'one call' bundling note but no format or edge-case detail beyond what the schema provides.

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?

States a specific verb and resource ('Creates a post, page, or any custom post type') and enumerates the fields it sets in one call. It also explicitly separates itself from the Elementor page-building tools, so an agent can route correctly without inspecting schemas.

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?

Explicitly says to use the Elementor tools instead when the goal is an Elementor page, which is a real routing decision an agent faces. It does not, however, discuss when to prefer draft vs. publish, or how this relates to the other post-creation siblings in the wider toolset.

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