wordpress_import_content

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Import content from WordPress XML,' which implies a write operation that could be destructive or require specific permissions, but it doesn't clarify behavioral traits such as whether it overwrites existing content, requires admin access, handles errors, or has rate limits. This is inadequate for a tool with potential side effects.

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 wasted words. It's front-loaded with the core action, making it easy to scan and understand quickly. This is an example of optimal conciseness for a simple tool.

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 (import operation with potential side effects), no annotations, no output schema, and 0% schema description coverage, the description is incomplete. It lacks details on behavior, parameters, return values, and error handling, making it insufficient for safe and effective use by an AI agent.

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?

The schema description coverage is 0%, and the description adds no parameter information beyond the tool's name. It doesn't explain the 'fileUrl' parameter (e.g., format, source, or constraints like requiring a valid XML file URL). With one undocumented parameter, the description fails to compensate for the schema's lack of details.

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 verb ('Import') and resource ('content from WordPress XML'), making the purpose specific and understandable. It distinguishes from siblings like 'wordpress_export_content' by indicating an import action, though it doesn't explicitly contrast with other import-related tools (e.g., 'wordpress_restore_backup' or 'wordpress_bulk_create_posts'), which prevents a perfect score.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a WordPress XML file), exclusions (e.g., not for other formats), or related tools like 'wordpress_export_content' for reverse operations. This lack of context leaves the agent without usage direction.

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