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

The description adds useful platform/type constraints, such as 'Subreddit is Reddit-only, hashtag is TikTok-only'. However, it does not disclose behaviors like whether removal is permanent, what happens if items do not exist, or what the response looks like. Since annotations already mark this as destructive and idempotent, the description adds some but not extensive additional transparency.

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 filler: the action, the required payload shape, and the prerequisite lookup. Each sentence contributes meaningful information, and the description is compact and readable.

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 removal tool, the description covers what to pass, valid enum combinations, platform restrictions, and how to list current items first. It does not document return values or failure behavior, but there is no output schema and the core invocation contract is clear.

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 description explains the item structure, the allowed type enum, the allowed platform enum, and the type-platform pairing rule. It also tells the agent to use getTrackedItems to obtain valid values. Internal metadata fields like _isTrial and feedback are not described, but those are not essential for invoking the tool 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?

Starts with 'Remove tracked keywords/users', which is a concrete verb + resource statement. It clearly distinguishes this from getTrackedItems and addTrackedItems among the siblings by making the removal semantics explicit.

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 gives explicit sequencing guidance: 'Use getTrackedItems first to see current items.' This tells the agent when and how to prepare the call. It does not explicitly say when not to use this tool, but the context is clear enough for selection.

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