Remove a media comment

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

Discloses key behaviors: removes comment, cascading deletion by default, option to refuse if replies exist, and returns removed ids. Adds value beyond the destructiveHint annotation.

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 sentences, front-loaded with the main purpose, followed by essential detail. No extraneous words.

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 simple deletion tool with annotations and no output schema, the description covers purpose, parameter behavior, and return value adequately. No missing critical information.

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) and explanation of cascade parameter behavior. With schema coverage at 25%, description compensates by clarifying two out of four parameters. Could mention name and project but still helpful.

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 specifies the source of the comment id from 'get_media / list_media_comments'. Distinguishes itself from siblings like add_media_comment and list_media_comments.

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 clear usage context by explaining the default behavior of removing reply subtree and how to change it via cascade parameter. Doesn't explicitly list when not to use but is sufficient for a deletion tool.

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