document_remove_request_body

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

With no annotations, the description should disclose behavioral traits. It mentions the OpenAPI version constraint but fails to note that removal is destructive (mutates the document), what happens if no request body exists, or any permissions required. The word 'remove' implies mutation but lacks detail.

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, concise sentence that immediately conveys the tool's purpose and constraint. There is no redundant or extraneous information; every word 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?

Given the tool's simplicity, the description is partially complete: it identifies the target and version. However, it lacks details about side effects (e.g., modification to the document in the session), return behavior (no output schema), and what occurs if the operation lacks a request body. This leaves gaps for a comprehensive 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 coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond the schema descriptions for path, method, and session. The schema already provides clear examples and definitions, so the description does not improve parameter understanding.

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 tool removes the request body from an operation, specifies it's for OpenAPI 3.x only, and the verb 'remove' combined with 'request body' precisely identifies the action and resource. It distinguishes itself from sibling tools like document_remove_operation or document_remove_parameter by targeting a specific component.

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 provides no explicit guidance on when to use this tool versus alternatives such as document_remove_operation or document_remove_node. It does not state prerequisites (e.g., the operation must exist and have a request body) or mention that this is the only tool for removing the request body.

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