hwp_delete_guide_text

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

No annotations provided, so description carries full burden. Discloses version history and extract_first option, but does not mention irreversibility, error behavior, or side effects. Sufficient for basic understanding but not comprehensive.

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?

Multiple sentences but mixes version info with usage. Could be more structured (e.g., separate behavioral notes from usage). Not extremely concise, but adequate length.

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; description does not explain return values or error states. For a 4-parameter tool with no annotations, it covers basic usage but lacks completeness regarding outcomes and edge cases.

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 100% (baseline 3). Description adds value by explaining scope enum values beyond schema, recommending defaults, and noting extract_first as a new feature. Provides context for patterns and table_keywords defaults.

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 deletes guide text in HWP forms, with specific verb 'delete' and resource 'guide text'. It distinguishes from sibling tool hwp_extract_guide_text by action (delete vs extract).

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?

Provides clear usage context: 'Use after filling out public institution forms before submission.' Recommends default scope='both' for general form cleanup. However, lacks explicit when-not-to-use or comparison to alternative deletion methods.

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