delete_field

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

The description explains the deletion of a full complex field, which is a clear behavioral trait. Without annotations, it carries the full burden and does so adequately. No contradictions.

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 concise with two sentences: one for the action and one for the parameter. No unnecessary words.

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 has one parameter and a clear action, the description is complete. It explains what the tool does, how to get the parameter, and is sufficient for correct invocation.

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?

With 0% schema description coverage, the description fully compensates by explaining the parameter: 'Positional identifier returned by list_fields' with an example. This adds significant meaning beyond the schema's bare string type.

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 it removes a complex field from the document, specifying 'complete complex field (begin through end runs)'. This distinguishes it from other deletion tools like delete_text or delete_paragraph.

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?

It mentions that field_id is returned by list_fields, providing clear context for when to use this tool. However, it does not explicitly state when not to use it or mention alternative tools for related field operations.

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