delete_comment

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool deletes a comment and returns a result dict, but fails to mention critical aspects like whether deletion is permanent, requires admin permissions, affects associated data (e.g., replies), or has rate limits. This is inadequate for a destructive operation.

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 extremely concise with three brief sentences that efficiently cover purpose, input, and output. It's front-loaded with the core action and wastes no words, making it easy for an agent to parse quickly.

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 the tool's complexity (a destructive operation with no annotations, 0% schema coverage, and no output schema), the description is incomplete. It omits essential details like behavioral traits (e.g., irreversibility, auth needs), parameter semantics, and output structure, leaving significant gaps for safe and effective use.

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 mentions the input parameter 'comment_id (str)', which aligns with the schema's single required parameter. However, with 0% schema description coverage, it doesn't add meaningful context beyond the schema (e.g., format of comment_id, where to find it, or validation rules). The baseline is 3 since the schema covers the parameter structure, but the description doesn't compensate for the lack of schema details.

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 clearly states the action ('Delete') and target ('a specific comment from the Page'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'delete_comment_from_post' or 'delete_post', which would require more specificity about the Page context versus other deletion targets.

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 provides no guidance on when to use this tool versus alternatives like 'delete_comment_from_post' or 'filter_negative_comments'. It lacks context about prerequisites, permissions, or scenarios where this deletion is appropriate, leaving the agent without usage direction.

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