clip_properties

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

No annotations are present, so the description bears full responsibility. It states the read nature and the conditional return of all properties. However, it does not disclose whether the operation is safe (non-destructive), what errors may occur, or if there are any side effects. The information is adequate but minimal.

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 extremely concise with two sentences, no extraneous words, and front-loads the core purpose in the first sentence. Every word earns its place, making it efficient for an agent to parse.

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, the description should hint at the return structure. It only says 'returns every property' without specifying format (e.g., key-value pairs, list). It also omits error behavior and required context (e.g., valid handle). The description is insufficient for a complete understanding.

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?

With 0% schema description coverage, the description must compensate. It partially explains the 'name' parameter (return all properties if omitted), but fails to describe the required 'handle' parameter. The description does not fully replace missing schema descriptions, leaving a notable gap.

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 reads clip properties, using the verb 'Read' and resource 'clip properties'. It distinguishes itself from sibling tools like clip_set_property by indicating it is a read operation, but does not explicitly differentiate from clip_metadata or other similar tools. The additional behavior 'Returns every property when name is omitted' provides clarity.

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 versus alternatives. It does not mention prerequisites (e.g., a valid clip handle) or situations where this tool is inappropriate. Without context, an agent may not know when to choose clip_properties over clip_metadata or clip_set_property.

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