delete_comment

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

Beyond the annotations, the description explains meaningful behavior: previews and confirmation are id-only because Splitwise cannot fetch a comment by id, and repeated deletion is treated as a no-op rather than a hard failure. This clarifies the idempotentHint annotation and gives an agent accurate expectations for edge cases.

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 front-loaded with the core action and then provides two tightly focused pieces of behavioral context. Every sentence adds necessary information without redundancy or unrelated detail.

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?

The description, together with the annotations and output schema, gives an agent everything needed to call this tool correctly: the destructive nature, idempotency behavior, confirmation semantics, and the limitation around previewing. No critical operational detail is missing.

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 input schema already documents both comment_id and confirm with 100% coverage, so the description does not need to redefine them. It adds context about the confirmation flow, but the parameters themselves are simple and well-covered by the schema.

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 opens with 'Permanently delete a comment,' which is a specific verb plus resource and clearly states the tool's destructive purpose. It also distinguishes itself from delete_expense by noting that no endpoint exists to fetch a single comment by id, making the tool's behavior unique among siblings.

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 clearly situates this tool as the way to delete comments and contrasts it with delete_expense, which helps an agent choose between those two destructive operations. It does not explicitly enumerate all when-to-use/when-not-to-use cases, but the context is clear enough for correct selection.

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