Remove a media comment

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

Discloses the default behavior of cascading deletion and the option to refuse deletion with replies. Also mentions the return value ('Returns the ids removed'). This adds value beyond the annotations which only indicate destructiveHint.

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?

Two concise sentences with no wasted words. Front-loaded with the primary action, and includes important behavioral nuance in the second sentence.

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?

Covers the main behavioral nuance (cascade) and return value. Could be improved by explaining the role of 'name' and 'project' parameters, but overall sufficient for a simple destructive tool with no output schema.

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?

Adds context for the 'id' parameter (source from other tools) and clarifies the 'cascade' parameter behavior. However, no additional meaning is given for 'name' and 'project' parameters, which have no schema descriptions, and schema coverage is low (25%).

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?

Clearly states the action 'Remove a comment by id' and references the source tools for obtaining the id. Differentiates from siblings like add_media_comment, but could be more explicit about its exclusive role versus other removal tools like remove_annotation.

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?

Provides guidance on using the cascade parameter, but does not explicitly state when to use this tool versus alternatives or mention prerequisites like permissions. The context is implied rather than stated.

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