marker_add

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

No annotations provided, so description carries full burden. It only states 'Add marker' without disclosing side effects, return values, or project context (e.g., whether marker is added to current project). Minimal behavioral information.

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?

Very concise: one line for purpose, one line for usage guideline, then a bullet list of arguments. Front-loaded with key info, no extraneous text.

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?

Given no output schema and 5 parameters, the description is too sparse. It lacks details on what happens when position overlaps, whether marker is added in the current project timeline, and any constraints or return values.

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 has 0% description coverage. Description adds meaning: 'position: Seconds' clarifies unit, 'color_r/g/b: Red/Green/Blue 0-255' specifies ranges, and 'name: Label' provides semantic context not in schema titles.

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 'Add marker' clearly indicates the action and object. It distinguishes this tool from 'add_markers_batch' for multiple markers, providing specificity.

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 description explicitly states 'Prefer add_markers_batch for multiple', guiding the agent on when to use alternative tool. However, it does not address other marker-related siblings like marker_add_region.

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