delete_comment

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

The description only mentions 'permanently', hinting at irreversibility, but lacks details on authentication requirements, associated effects (e.g., card updates), error cases, or rate limits. With no annotations, the description bears the full burden and is insufficient.

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?

Extremely concise (5 words), but at the cost of necessary context. Not verbose, but under-specified. Front-loaded with action.

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 one parameter and an output schema, the description is adequate but lacks mention of what constitutes a comment (e.g., card comment vs board comment) and the return value. Could be more complete.

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 does not explain the comment_id parameter, its format, or how to obtain it. Schema coverage is 0%, leaving the agent with no guidance beyond the basic type.

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), the resource (Trello comment), and specifies permanence. It is distinct from sibling tools like update_comment or list_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?

No guidance on when to use this tool versus alternatives, such as soft-deleting or hiding a comment. No prerequisites or exclusions mentioned.

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