delete_listing_file

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

No annotations provided, so the description carries full burden. It only states 'Remove', which implies deletion, but does not disclose whether the action is irreversible, permissions needed, or side effects. For a destructive tool, more transparency is expected.

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 sentence, which is concise. It is front-loaded with the action. However, it is too minimal and could include more context without becoming verbose.

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?

Given two required parameters with no descriptions or enums, no output schema, and no annotations, the description falls short. It does not explain the effect on the listing or what success looks like, leaving the agent with insufficient context.

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%, so the description should compensate by explaining parameters. However, it does not add any meaning beyond what the parameter names (listing_id, listing_file_id) imply. No additional semantics about what constitutes a valid ID or how to obtain them.

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 'Remove a digital file from a listing' clearly states the action (remove) and the resource (digital file from a listing). It distinguishes from sibling tools like delete_listing (removes listing) and delete_listing_image (removes image) implicitly, but could be more explicit about the file vs image distinction.

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?

No guidance on when to use this tool versus alternatives such as delete_listing_image or upload_listing_file. The description does not provide any context for selection or prerequisites.

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