edit_task_comment

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

No annotations are provided, so the description carries the full burden. It only states the basic edit action and does not disclose what happens to the original content, whether edits are partial or full replacements, or any error behavior for nonexistent comments.

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 a single concise sentence with no wasted words. It delivers the essential purpose immediately and is appropriately sized for a straightforward edit operation.

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 mutating tool with no annotations and no output schema, the description is minimal. It fails to explain key behavioral details such as idempotency, failure modes, or whether the content replaces the entire comment, leaving the agent without enough context to use the tool safely in edge cases.

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 provides complete descriptions for all four parameters (project_id, task_id, comment_id, content), achieving 100% coverage. The description adds little beyond the schema, but the schema already clearly documents what each parameter means.

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 'Edit an existing comment on a task' uses a specific verb ('Edit') and identifies the exact resource (existing comment on a task). It clearly distinguishes this tool from siblings like add_task_comment and delete_task_comment by implying the comment already exists.

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 phrase 'existing comment' implies this tool should be used when the target comment already exists, as opposed to adding or deleting. However, there is no explicit guidance about when to prefer this over alternatives or what conditions must be met before editing.

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