Create a canonical page with provenance.
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| error | No | ||
| replayed | No | ||
| operation | No | ||
| truncated | No | ||
| next_cursor | No |
Changes observed during successful MCP inspections.
Input schema / properties / data / properties / body / descriptionPrevious value: -"Task-specific text the user intends to store for the selected audience; no full chat transcripts, credentials or restricted personal records. Non-empty, at most 20 KiB UTF-8 (replies/evidence at most 10 KiB)."New value: +"Task-specific text the user intends to store for the selected audience. Non-empty, at most 20 KiB UTF-8 (replies/evidence at most 10 KiB)."Input schema / properties / data / properties / body / descriptionPrevious value: -"Text to store. Non-empty, at most 20 KiB UTF-8 (replies/evidence at most 10 KiB)."New value: +"Task-specific text the user intends to store for the selected audience; no full chat transcripts, credentials or restricted personal records. Non-empty, at most 20 KiB UTF-8 (replies/evidence at most 10 KiB)."Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": true,
+ "description": "Structured result for create_knowledge_page. Resource fields vary by detail, permissions and operation. Paginated results use items/next_cursor; operation-key replays use operation/replayed. Failures have error and the MCP result has isError=true. See get_help for this tool's contract.",
+ "properties": {
+ "error": {
+ "properties": {
+ "code": {
+ "type": "string"
+ },
+ "help": {
+ "type": "string"
+ },
+ "message": {
+ "type": "string"
+ },
+ "next_action": {
+ "type": "string"
+ },
+ "retry_after_seconds": {
+ "type": "integer"
+ }
+ },
+ "required": [
+ "code",
+ "message",
+ "next_action",
+ "help"
+ ],
+ "type": "object"
+ },
+ "next_cursor": {
+ "type": "string"
+ },
+ "operation": {
+ "type": "object"
+ },
+ "replayed": {
+ "type": "boolean"
+ },
+ "truncated": {
+ "type": "boolean"
+ }
+ },
+ "type": "object"
+}Input schema / properties / data / properties / operation_keyAdded value: +{
+ "description": "Optional stable client key scoped to this agent for 30 days. Reuse identical payload after a timeout. Different payload conflicts. Retry returns compact operation receipt, not original body. Distinct from diagnostic request_id; existing create-space request_id remains required.",
+ "maxLength": 80,
+ "pattern": "^[a-z0-9]+(-[a-z0-9]+)*$",
+ "type": "string"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false and destructiveHint=true, so the core write/destructive nature is covered. The description adds little behavioral context: it does not explain whether an existing page is replaced, how provenance is captured, or what side effects occur beyond the vague phrase 'with provenance.'
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?
At six words, the description is concise and front-loaded with the action and object. However, for a tool with complex nested inputs and many sibling tools, this brevity becomes under-specification rather than efficient structure.
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 complex nested schema, destructive annotation, and large sibling set, a one-line description is insufficient. It does not explain what a knowledge page is, when to use this tool, or how it relates to similar creation tools, even though an output schema is present.
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 description contains no parameter information, and schema description coverage is reported as 0% for the required data parameter. While the nested schema provides detailed field descriptions, the description itself does not compensate by showing how to structure an invocation or what the data object represents.
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') and names a specific resource ('canonical page'), so the basic action is clear. However, 'canonical' and 'provenance' are not explained, and the description does not differentiate this tool from siblings like create_post or create_space_entry aside from the name.
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 guidance is provided about when to use this tool versus alternatives. There is no mention of conditions, prerequisites, or exclusions, so an agent receives no routing information from the description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.