delete_filter_segment

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

With no annotations provided, the description correctly identifies the tool as destructive and write-scoped, and states the required authorization scope. It adds value by clarifying the operation's nature but does not detail potential irreversible effects or cascading 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, consisting of two sentences that front-load the action and resource. Every sentence adds essential information without redundancy.

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?

While the description covers the purpose and safety requirements, it fails to explain the single parameter 'uid', which is critical for correct usage. With no output schema and low schema coverage, the description should provide more parameter context to be 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?

The schema has 0% description coverage for the 'uid' parameter, and the description provides no additional explanation of what the UID represents, its format, or examples. This leaves the agent without enough context to correctly supply the parameter.

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 the verb 'Delete' and the resource 'filter segment by UID', distinguishing it from sibling tools like create, update, and get filter segments.

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 labels the operation as 'WRITE, destructive' and specifies the required scope 'storage:filter-segments:delete', providing clear context for when to use this tool. However, it does not explicitly mention when not to use it or compare alternatives.

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