delete_dictionary_override

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

Since no annotations are provided, the description carries full burden. It discloses that deletion is immediate, requires confirmation, and gives an example of behavioral change (mandatory field becoming optional). Does not mention auth needs or rate limits but covers key behavioral aspects well.

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?

Description is three sentences with clear structure: purpose, safety note, prerequisite. Every sentence provides value. No fluff. Front-loaded with primary action.

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 3 parameters, no output schema, and no annotations, the description covers purpose, safety, and prerequisite. Does not explain return values or error cases, but for a straightforward delete operation, it is reasonably complete.

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 baseline is 3. The description mentions 'Find the sys_id first' which is not a parameter in the schema (tool uses table and field instead). This minor inconsistency may confuse agents but does not detract from parameter meaning. Description adds little beyond schema explanations.

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 tool deletes a dictionary override and explains the effect (restoring parent defaults). The verb 'delete' and resource 'dictionary override' are specific. Sibling tools 'create_dictionary_override' and 'get_dictionary_overrides' are distinct, so purpose is well-differentiated.

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?

Description provides explicit safety requirement (confirm=true) and prerequisite (find sys_id with get_dictionary_overrides). It implies the tool is used to revert overrides but does not explicitly state when to avoid using it or compare to alternatives. Still clear enough for practical use.

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