delete_marker

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

The annotation destructiveHint=true already indicates the destructive nature. The description simply restates 'delete' without adding extra context such as permanence, undoability, or side effects. It is consistent with the annotation but adds no additional transparency beyond it.

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, front-loaded sentence that directly states the action and target. There is no extraneous information, making it highly concise and well-structured.

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 one-parameter destructive tool, the description is minimal but adequate for a basic call. It does not explain how to obtain the index or any indexing conventions, which could be important for correct usage. Given the simplicity, a score of 3 reflects that it is functional but lacks deeper context.

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 schema provides no description for marker_index (0% coverage). The description clarifies that marker_index is the index of the marker to delete, which adds meaning beyond the raw schema. However, it does not specify whether the index is zero-based or how to retrieve it, so it is not fully comprehensive.

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 (marker), and how to identify it (by index). This distinguishes it from siblings like delete_region and add_marker, making the purpose unambiguous.

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. It does not mention that the index should be obtained from get_markers, nor does it provide any prerequisites or exclusions. The description is purely declarative with no contextual instructions.

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