seo_import_settings

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: not whether importing overwrites or merges existing settings, whether the operation is reversible, what permissions are needed, or what payload format 'data' requires. 'Import' weakly implies a write, which is the only signal available.

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?

A single short sentence with zero redundancy, so nothing is wasted. However, the brevity is under-specification rather than efficient conciseness, and there is no front-loaded scoping constraint to guide the call.

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 mutation tool with no annotations, no output schema, and an untyped nested payload, the description should at minimum say what happens to existing settings and what 'data' must contain. Neither is present, leaving the agent unable to call this safely or confidently.

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%, so both parameters ('site' and 'data') are documented in the schema, which sets the baseline at 3. The description adds no meaning beyond the schema, and the free-form 'data' object with additionalProperties and no shape hint is left equally opaque in both places.

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 restates the tool name nearly verbatim: 'seo_import_settings' → 'Import cvrt-seo-manager settings.' The only added token is the vendor qualifier 'cvrt-seo-manager', which does not clarify what settings are imported or distinguish this from seo_import_migrate, seo_import_csv, or seo_import_redirects.

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 when-to-use guidance, no prerequisites, and no mention of the four sibling import/export tools (seo_import_migrate, seo_import_csv, seo_import_redirects, seo_export_settings) that an agent must choose between. Nothing tells the caller when this tool is the right one.

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