add_layer_marker

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

No annotations or description of side effects, permissions, or return values. The description is purely functional without any behavioral detail.

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 redundancy. It directly states the tool's function.

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 is minimal and lacks context such as error conditions, success indicators, or interaction with other tools. No annotations or output schema further reduce completeness.

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?

Parameter names are suggestive (e.g., time, compId, comment, duration, layerName, layerIndex), but there are no descriptions and schema coverage is 0%. The description does not compensate, so semantics remain largely ambiguous.

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 ('Add a marker') and target ('to a layer'), but it does not specify how the layer is identified (e.g., by name or index) or distinguish it from similar tools like add_composition_marker. The core purpose is understandable.

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 usage guidelines are provided. There is no mention of prerequisites, constraints, or when this tool should be used instead of alternatives.

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