workiva_delete_document_section

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

The description offers no behavioral context beyond the verb 'Delete'. It does not disclose permanence, permissions, or effects on child content. With no annotations provided, the description fails to carry the transparency burden, though the destructive nature is implied by the verb.

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 extremely concise: one action line plus a clean Args section. It is front-loaded and every word earns its place, though it is so brief that it borders on under-specification. For a simple delete tool, this level of conciseness is acceptable.

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 description omits critical context for a destructive operation, such as whether deletion is permanent or reversible, and there are no annotations to supplement. The output schema exists, but the description does not address side effects or any prerequisites, making it incomplete for a delete tool.

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 adds 'The document UUID' and 'The section UUID', clarifying the parameter formats beyond the schema's bare titles (Document Id, Section Id). However, it does not explain how to obtain these IDs or any constraints, leaving partial compensation for the 0% schema description coverage.

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 states 'Delete a document section' with a clear verb (Delete) and resource (document section). It is unambiguous and distinguishes from sibling tools like get, create, copy, and bulk_edit on document sections.

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 guidance on when to use this tool versus alternatives, such as bulk_edit_document_sections or copy_document_section. It simply states the action without any context on appropriate usage or exclusions.

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