Update multiple Outline wiki documents simultaneously to modify titles, content, or append text in bulk operations.
Update multiple documents at once.
| Name | Required | Description | Default |
|---|---|---|---|
| updates | Yes |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden but only states the basic operation. It doesn't disclose permissions needed, whether updates are atomic/partial, error handling for failed updates, rate limits, or what happens to documents not in the updates array. 'Update' implies mutation but lacks behavioral details.
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?
Extremely concise with a single sentence that directly states the tool's purpose. No wasted words or unnecessary elaboration, though this conciseness comes at the cost of detail.
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 batch mutation tool with 1 parameter (complex array), 0% schema coverage, no annotations, and no output schema, the description is inadequate. It doesn't explain the updates parameter structure, return values, error conditions, or how it differs from sibling batch tools, leaving significant gaps for agent understanding.
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 but only mentions 'multiple documents' without explaining the updates array structure or parameters like documentId, title, text, append. It adds minimal value beyond the schema's property names, failing to clarify parameter meanings or usage.
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 clearly states the action ('update') and resource ('multiple documents'), with 'at once' implying batch processing. It distinguishes from single-document updates but doesn't explicitly differentiate from other batch operations like batch_archive_documents or batch_delete_documents.
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 on when to use this tool versus alternatives like update_document for single updates or other batch operations. The description implies batch context but provides no explicit when/when-not criteria or prerequisite conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.