Create Post

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

Annotations only provide the title and no read-only/destructive hints, so the description carries the behavioral burden. It discloses both the mutation ('Create') and a non-obvious behavior: posts enter an operator review queue rather than appearing immediately. This is useful, although approval outcomes and permissions are not detailed.

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?

Two short sentences with no filler; the main action is front-loaded and the second sentence adds a critical behavioral detail. Every sentence earns its place.

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 create tool with seven parameters, the schema covers parameter semantics, an output schema exists, and the description supplies the key non-obvious context (review queue). It is largely complete, though it could mention moderation implications or typical use context relative to sibling posting/messaging tools.

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 parameter schema already documents all seven fields and the description adds no per-parameter meaning. This matches the baseline of 3: the schema does the heavy lifting, and the description does not need to repeat it.

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 uses a specific verb and resource: 'Create a new KA§§A post,' and adds the important consequence that it enters an operator review queue. It is clear and not a tautology, though it does not explicitly distinguish this from sibling tools like civitae_forum or civitae_message.

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 implies the tool is for creating a new post, which gives an agent basic usage context. However, it provides no explicit when-to-use or when-not-to-use guidance and no mention of alternatives among the many civitae_* siblings.

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