attach_custom_property

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not mention side effects, required permissions, reversibility, or what happens when the operation is invoked. The phrase 'expanded operation' is ambiguous and does not clarify whether this is a read or mutation action.

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 short, but this is under-specification rather than conciseness. It does not front-load essential information; it merely restates the tool name with a vague qualifier. A concise description should still convey key details, which this entirely lacks.

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 likely requires domain-specific knowledge about custom properties in Premiere Pro, but the description provides none. There is no output schema or annotation to fill the gap. The description is inadequate for an agent to invoke this tool correctly or understand its role among 200+ sibling tools.

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 allows arbitrary properties but defines none, so schema description coverage is vacuous. Despite a baseline of 3 for high schema coverage, the description adds no meaning to the input parameters. It does not indicate what fields are expected (e.g., clip ID, property name/value), leaving the agent without guidance for constructing valid arguments.

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 merely restates the tool name ('attach custom property') without explaining what the operation does. It adds only the boilerplate phrase 'Premiere Pro expanded operation', which provides no concrete verb or resource distinction from the many sibling tools. It fails to establish a clear purpose.

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 is given on when to use this tool versus alternatives. The description lacks any context about typical use cases, prerequisites, or exclusions. It offers no support for an agent to decide between attach_custom_property and similar tools like add_custom_metadata_field.

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