attach_custom_property

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention side effects, requirements, reversibility, permissions, or what constitutes success. A single vague sentence is completely inadequate.

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 short, but brevity is not value. It contains no concrete, actionable information, so it reads as under-specified rather than concisely effective. It does not earn its place.

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 that presumably attaches a custom property (likely requiring property name and value) with no output schema, the description is severely incomplete. An agent has no idea what the tool does, what inputs it expects, or what the result would be.

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 input schema defines zero named parameters (though it allows arbitrary additional properties), so the description must explain what properties an agent should supply. It does not, leaving the caller entirely in the dark about required arguments like the property name and value.

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 states a verb ('attach') and a resource ('custom property'), but 'custom property' is undefined and the target of the attachment is unclear. It does not distinguish this tool from siblings like add_custom_metadata_field or set_xmp_metadata, and the phrase 'Premiere Pro expanded operation' is generic filler.

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 versus alternatives, no mention of prerequisites, and no exclusions. The description provides zero guidance on the context in which an agent should invoke it.

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