wordpress_import_content

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

No annotations exist, so the description carries the full burden. It fails to disclose whether the import overwrites existing data, requires authentication, or what side effects occur. The one-sentence description gives no behavioral detail beyond 'import'.

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 quite short and front-loaded, but it is under-specified rather than efficiently complete. It is a single sentence with no waste, but it omits critical details, making it more terse than concise.

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?

With only one parameter, no annotations, no output schema, and no explanation of return values, side effects, or import scope, the description is completely inadequate. The agent would have no idea what to expect or how to handle edge cases.

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 0% and the description does not explain the fileUrl parameter beyond its name. The tool sends no semantic information about what the URL should point to (e.g., remote file, upload, format constraints).

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 imports content from WordPress XML, which is a specific verb and resource. It distinguishes from content creation/export tools, though it doesn't specify the exact scope of 'content' (e.g., posts, media, settings).

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 is provided on when to use this tool versus alternatives like wordpress_export_content or bulk creation tools. The description implies usage for importing XML, but no explicit when-to-use or exclusion context.

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