set_notify_time

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

No annotations are provided, so the description must disclose behavior. It states the action (setting trigger time) but does not disclose whether the asset is permanently modified, whether the notify must already exist, or any error conditions. It transparently describes the core mutation but omits broader behavioral context.

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 two clear sentences plus a structured argument list. Every sentence and line is necessary and directly valuable, with no redundancy or fluff.

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 a simple setter with three required parameters and an existing output schema. The description covers the action and all parameter semantics. It could be enhanced with a note about modifying the asset, but given the simplicity, it is reasonably complete.

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?

All three parameters are explained in the Args section with concrete meaning: asset_path as 'Unreal asset path', notify_index as 'Index of the notify', and new_time as 'New trigger time in seconds' (provides units). This fully compensates for the schema's lack of descriptions, which only supply titles like 'New Time'.

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 'Set the trigger time of a specific notify' with a specific verb and resource, and the inclusion of asset_path, notify_index, and new_time makes it clear this affects a single notify in an asset. It differentiates from siblings like set_notify_duration and remove_notifies.

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 explicit guidance on when to use this tool versus setting duration or adding notifies. It implies usage only through its name and description, but does not mention alternatives or exclusions. This is adequate but uninformative for selection among sibling set_* and notify tools.

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