bookshelf_delete_customfilter

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

The description explicitly says 'DESTRUCTIVE: this deletes data,' which aligns with the destructiveHint annotation. However, it adds little beyond the annotation, lacking specifics about what data is deleted (e.g., the custom filter itself, associated data) or any consequences.

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 brief and front-loaded, but it is under-specified. Both sentences carry some value (action and destructiveness), yet critical parameter information is missing, making it not appropriately sized for the tool's needs.

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 tool, the description covers the basic action but omits parameter semantics and usage context. The output schema exists, so return values are not needed, but the missing 'id' explanation leaves the tool incomplete for proper 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?

The schema has one required integer 'id' with no description, and schema coverage is 0%. The description does not mention the 'id' parameter at all, failing to explain what it identifies. The agent would have to guess that 'id' refers to the custom filter's identifier.

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 customfilter' clearly states the action and resource. It is direct and unambiguous, though it doesn't differentiate from other delete tools beyond the resource name, which is inherent.

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, nor any context about prerequisites or exclusions. An agent cannot determine the appropriate scenario from the description alone.

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