Import Markdown

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

Annotations already declare openWorldHint=false and destructiveHint=false, lowering the bar. The description usefully discloses the per-page frontmatter surface that controls behavior (title, slug, folder, template, published, publish_at), but says nothing about auth/permission needs, slug or path collisions, validation/error behavior, or whether the import runs synchronously or creates a job (relevant given list_import_jobs/get_import_job exist as siblings).

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 purpose, then capabilities, then a compact worked example. Every element earns its place; the example is the one slightly long block, but it directly enables correct invocation.

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?

There is no output schema, and the description never says what comes back or how progress/completion is observed, which matters for a bulk import in a system that exposes import jobs. Frontmatter behavior is well covered, but the post-invocation contract is left implicit.

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 the baseline is 3, and the description exceeds it: it enumerates the frontmatter keys that actually drive per-page configuration (crucial because the schema's 'content' param only hints at frontmatter) and supplies a concrete frontmatter example. This meaningfully augments the schema for the highest-leverage parameter.

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 ('Import one or more Markdown pages into LightCMS') and scopes it as a bulk operation, which separates it conceptually from single-page tools like create_content. It does not explicitly name or rule out the closest siblings (import_csv, bulk_create_content, create_import_source), so the agent must infer the boundary from the 'Markdown/frontmatter' framing.

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?

'Ideal for bulk content creation by AI agents' gives a positive usage signal, but there is no when-not guidance and no named alternative for other import paths (CSV import, single-page creation, import sources/jobs). Usage is implied rather than contrasted.

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