delete_comment

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

Discloses ownership constraint, which is important behavioral info beyond the verb 'delete'. With no annotations, this partially fulfills transparency, but lacks details like irreversibility or permissions.

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?

Efficient one-sentence description with clear main point, though could include a bit more context without harming conciseness.

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 action and key condition, but lacks details on error scenarios, prerequisites (e.g., comment must exist), or what happens after deletion, especially given the existence of an 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?

The description adds no meaning to the single parameter 'comment_id' beyond its name. With 0% schema coverage, it should describe how to obtain or format the ID.

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 (delete) and resource (comment) with a specific condition (owned by caller), distinguishing it from sibling tools like delete_event_occurrence_comment.

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 a usage condition (owned by caller) but no explicit guidance on when to use vs alternatives like delete_event_occurrence_comment.

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