register_content_package

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

With no annotations, the description must carry the behavioral disclosure burden. It does reveal the append-only nature of the record, but it does not disclose authentication requirements, duplicate-slug handling, whether artifacts can be updated later, failure modes, or what response to expect.

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 front-loaded sentence with no filler. It states the core operation, the record type, and the main content categories immediately.

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?

The tool is complex: 10 parameters, nested objects, no output schema, and no annotations. One sentence is insufficient to guide an agent on required fields, artifact semantics, metadata fields, or expected behavior. The description provides a high-level purpose but not enough operational context.

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 0%, so the description must compensate. It groups some parameters under 'local artifacts' and 'editorial retrieval metadata,' but it does not explain the required slug, title, content_type, or the nested artifacts structure. Ten parameters are largely left to the agent to infer from names alone.

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 ('Create') with a distinct resource ('append-only Clearon content record') and adds scope ('local artifacts and editorial retrieval metadata'). This differentiates it from sibling tools that get, search, update, or record publication-related events.

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 use for creating new content records and the 'append-only' wording suggests it is not for updating existing records. However, it does not explicitly state when to use this tool versus update_content_artifacts, record_publication, or search/retrieval siblings.

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