fields_bulk_delete_organization_fields

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

No annotations are provided, so the description must fully disclose behavioral traits. It states the destructive action (delete) but does not mention authorization requirements, reversibility, error handling, or any constraints beyond input format.

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?

Three sentences with no extraneous information. The first sentence states the purpose, followed by bullet-like format details and a concluding note on normalization. Every sentence 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 one parameter and no output schema, the description covers purpose and input format adequately. However, it omits typical behavioral info (rate limits, success response, error cases) that would be helpful for a destructive operation with no annotations.

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 schema already defines the parameter with a oneOf type and pattern, but the description adds value by clarifying that both comma-separated strings and numeric arrays are accepted and normalized to a query parameter, which helps the agent prepare the input correctly.

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 starts with 'Delete multiple custom organization fields in a single request,' clearly stating the verb (delete), resource (custom organization fields), and bulk nature, distinguishing it from the sibling single-delete tool.

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 explains the accepted input formats and normalisation, implying when to use this tool (for bulk deletion), but lacks explicit guidance on when not to use it or alternatives like the single delete.

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