delete_paragraph
Delete a paragraph from a Word document by specifying its index. Removes the paragraph at the given position.
Instructions
Delete a paragraph by index
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| doc_id | Yes | ||
| paragraph_index | Yes |
Delete a paragraph from a Word document by specifying its index. Removes the paragraph at the given position.
Delete a paragraph by index
| Name | Required | Description | Default |
|---|---|---|---|
| doc_id | Yes | ||
| paragraph_index | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It states 'delete' which implies destructive action, but lacks details on reversibility, effect on indices, permissions required, or error handling.
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 very concise (one sentence), but lacks necessary detail. It is efficient but at the expense of completeness.
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?
No output schema, no annotations, and only 2 parameters. Description is too minimal for a destructive operation; fails to specify behavior for out-of-range index or locked documents.
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%. Description adds minimal meaning beyond schema; it doesn't explain 'doc_id' or whether 'paragraph_index' is zero-based or one-based.
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?
Description clearly states the verb 'delete' and resource 'paragraph', and specifies the parameter 'index'. This distinguishes it from sibling tools like 'add_paragraph' or 'delete_document'.
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. For example, there are other deletion tools like 'delete_document', but no mention of when to choose one over the other.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/aspose-words/Aspose.Words-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server