delete_custom_format

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only states the delete action and does not disclose whether deletion is permanent, whether it can fail due to dependencies (e.g., custom format in use by a release profile), or any other side effects. This is a minimal disclosure for a destructive operation.

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 a single concise sentence that states the action and resource with no unnecessary words. It is front-loaded with the verb 'Delete' and carries the core meaning immediately.

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?

For a simple delete operation with one parameter and no output schema, the description combined with the schema is largely sufficient for an agent to invoke the tool correctly. However, it omits any operational context such as permanency or failure conditions, which would make it fully 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 description coverage is 100% and the single required parameter 'id' is described as 'Custom format id' in the schema. The description adds no additional parameter meaning beyond what the schema already provides, so the baseline score of 3 applies.

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 'Delete a custom format' uses a specific verb and resource, making the tool's purpose unambiguous. It clearly distinguishes from sibling tools like create_custom_format, update_custom_format, get_custom_format, and list_custom_formats by focusing on the delete action.

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. It does not mention prerequisites, when not to use it, or how to choose between delete_custom_format and update_custom_format or other delete operations. The only implied guidance is the tool's name, which is insufficient for the agent to make a fully informed choice.

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