item_get_properties

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

With readOnlyHint=true, the safety profile is already covered. The description adds that the result is a collection of key-value pairs and that it includes all properties, which is useful behavioral context beyond the annotation. However, it does not mention edge cases like missing items or performance implications, which are not needed for a simple read.

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, clear sentence that immediately conveys the resource (timeline item), the action (return all properties), and the output format (key-value pairs). No wasted words or redundant details.

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 tool is simple, read-only, and its output schema is present (as indicated by the context signals), so the description need not explain return values in depth. The description fully covers the purpose and result for this getter tool.

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 description coverage is 100%, so the schema fully documents each parameter (item_name, track_type, track_index). The description adds no additional parameter-level explanation, so it does not enhance the schema. Baseline 3 is appropriate.

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 tool returns all properties of a timeline item as key-value pairs. This distinguishes it from siblings that return specific properties (e.g., item_get_name, item_get_duration) and from clip_get_properties, which returns properties for clips rather than timeline items.

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 implies use when all properties of a timeline item are needed, but it does not explicitly compare to alternatives or state when not to use it. No sibling tools are mentioned, so the agent must infer context from the wording.

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