get_project_item_markers

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

With no annotations, the description carries the full behavioral burden and provides almost nothing: no statement that this is a read-only retrieval, no return shape, no note about what counts as a 'marker' or whether media type affects results. Only the implicit noun phrase suggests a read operation.

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?

It is short, but the brevity comes from under-specification rather than efficient front-loading. There is no leading verb phrase or actionable information for the agent to anchor on.

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 tool with no annotations, no output schema, and a fully undocumented required parameter, the description is far too thin. An agent would need outside knowledge of the host application to use this reliably.

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 coverage is 0% and the description never mentions nodeId. An agent cannot tell from either source whether nodeId is a project item node ID, a bin item ID, or a media file identifier, which is critical for calling correctly.

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 fragment 'Markers on a project item's media' identifies the resource but supplies no verb and reads as a restatement of the name rather than a stated action. It does not distinguish itself from siblings like get_markers or get_clip_markers, which cover adjacent marker scopes.

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?

There is no indication of when to use this tool instead of get_markers, get_clip_markers, or the add/remove marker siblings. The agent must infer usage entirely from the tool name.

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