get_sync_markers

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

No annotations are present, so the description must carry the full burden of behavioral disclosure. It states the tool gets sync markers but does not mention whether it is read-only, error behavior, or constraints on the asset_path format. The verb 'get' hints at a read operation, but side effects and failure modes are unaddressed.

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 very concise, with one sentence and an args list. It is well-structured for a tool of this simplicity, avoiding redundant wording. It could have been slightly more informative without becoming bloated.

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?

With only one parameter, no annotations, and an output schema, the description is too minimal to be fully complete. It lacks context about asset path conventions, asset type restrictions, and when to prefer this tool over sibling getters. The description barely covers the essentials.

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 has only a title for asset_path, so the description's parameter explanation is crucial. It merely repeats 'Unreal asset path' without offering format examples, path conventions, or constraints beyond the string type. This adds minimal value over the schema.

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 identifies the action as retrieving sync markers from an animation sequence, using a specific verb and resource. It distinguishes itself from sibling getter tools by naming the exact data type targeted.

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 provides no guidance on when to use this tool, prerequisites, or how it relates to alternatives like get_anim_sequence_info or add_sync_marker. The name implies usage, but no explicit direction is given.

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