marker_remove

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

With no annotations, the description carries the full burden of behavioral disclosure, and it only states that the marker is removed. It does not disclose whether removal is permanent, whether it affects timeline state, whether it can be undone, or what happens if the ID is invalid.

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 short sentence with no filler or repetition. The action and target are front-loaded, and the structure is appropriately sized for a simple one-parameter removal tool.

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 removal tool, the description is minimally sufficient: an agent can infer the call shape from marker_id and the verb 'remove'. However, with no annotations or usage guidance, it leaves room for ambiguity about the context of markers and the operation's side effects.

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?

Schema description coverage is 0%, but the phrase 'by ID' clarifies that marker_id is the selector used to identify the marker. This is minimal compensation for a single obvious parameter, though it adds little beyond the schema's marker_id property name and integer 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 'Remove marker by ID' uses a specific verb and resource, clearly indicating the action and the key input. It doesn't explicitly contrast with sibling tools, but the target is unambiguous and distinct from marker_add and marker_list.

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 given about when to use this tool versus alternatives, such as needing to look up the marker ID via marker_list first. There are no stated prerequisites, exclusions, or conditions that would help an agent decide between this and related marker tools.

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