remove_spam_listing

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

Annotations are absent, so the description carries the full burden. It identifies the target of the operation ('spam listing info') but does not disclose whether the action is irreversible, what side effects occur, whether confirmation is required, or what happens to related data. 'Remove' is the only behavioral signal, and it is essentially the tool name restated.

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 short and front-loaded, with no filler, so it earns credit for conciseness. However, it is so terse that it functions almost as a restatement of the tool name and provides minimal additional value.

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?

Although an output schema exists and removes the need to explain return values, the description is still incomplete. With no annotations, no parameter descriptions, and no behavioral details, an agent lacks crucial context about what zoid and spam_data should be and what removal entails.

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 0%, and the description does not explain the two required parameters. 'zoid' is not defined in the schema or description, and 'spam_data' is only a generic object with additionalProperties allowed, so the agent cannot determine what shape or values are expected.

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 states the action (removing) and the resource (organization spam listing info), which is enough to distinguish it from sibling tools like get_spam_listing_info and update_spam_listing. However, 'spam listing info' is slightly ambiguous about whether it deletes the listing itself or some associated metadata.

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?

There is no guidance on when to use this tool versus its alternatives. The description only states what it does, leaving the agent to infer that it is appropriate for deleting spam listing data. No exclusions, prerequisites, or alternative tools are mentioned.

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