delete_job_comment

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

With no annotations, the description must convey behavioral traits. 'Delete' implies mutation and irreversibility, but no details are given about permissions, side effects, or confirmation. The agent cannot assess the impact of using this tool.

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 too brief (four words) and under-specifies the tool's behavior. While it is front-loaded, it lacks critical detail that warrants additional sentences, making it insufficient rather than concise.

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?

Despite having a simple interface with two parameters and an output schema, the description omits any explanation of return values, error conditions, or parameter constraints. The agent is left with minimal context to correctly invoke the tool.

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 has two required integer parameters with no descriptions, and the tool description offers no explanation of what job_id and comment_id represent or how they relate. Since schema description coverage is 0%, the description fails to add any meaning to the parameters.

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 the resource 'a job comment', which differentiates it from sibling tools like add_job_comment, update_job_comment, and get_job_comments. However, it lacks specificity such as indicating that the comment is identified by job_id and comment_id.

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 is provided on when to use this tool versus alternatives like update_job_comment or cancel_job. There is no mention of required prerequisites or context, leaving the agent to infer usage from the name alone.

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