markers_get

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

With no annotations, the description carries full burden but only states basic function. It does not disclose whether it returns all markers, requires a specific timeline, or includes subclip markers. Lacks behavioral context.

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 short (one sentence) and front-loaded with core action. However, it fails to earn its place by omitting parameter info, making it slightly under-informative for the tool's complexity.

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 one undocumented parameter and no output schema, the description is insufficient. It does not explain filtering, output format, or relationships to timeline context, leaving gaps for effective agent usage.

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 sole parameter 'name_or_handle' is undocumented in both schema and description. Schema coverage is 0%, and the description adds no meaning, leaving the agent unable to understand its purpose or usage.

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 'List timeline markers, sorted by frame.' It specifies the action (list) and resource (timeline markers) with an additional detail (sorted by frame). It distinguishes from siblings like marker_add and marker_delete, though could be more explicit about which timeline it refers to.

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 on when to use this tool vs. alternatives like clip_markers or marker_add. The description does not mention context or exclusions, leaving the agent without direction for selection among siblings.

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