set_notify_duration

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only states the obvious mutation ('Set') without mentioning side effects, validation, asset-save requirements, or error handling. This does not provide meaningful transparency beyond the operation itself.

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 concise, front-loaded with a clear purpose statement, and followed by a structured Args list. Every line earns its place with no fluff, making it easy for an agent to quickly parse the essential information.

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 simple setter with three basic parameters, the description covers the core purpose and parameter meanings adequately. However, it omits usage context, behavioral details, and any mention of return values or error conditions, leaving gaps that are not filled by the existing output schema or annotations. It is minimally viable but not thorough.

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 Args section adds brief meaning beyond schema titles: it clarifies asset_path as 'Unreal asset path', notify_index as 'Index of the notify state', and new_duration as 'New duration in seconds'. This partially compensates for the 0% schema description coverage, though it lacks constraints like allowed ranges or path formats.

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 opens with 'Set the duration of a notify state,' clearly identifying the action (set) and the resource (duration of a notify state). This specific verb+resource combination differentiates it from sibling tools like set_notify_time or add_notify, making the purpose unambiguous.

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 guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The description solely states what it does without any contextual 'when' or 'when not' information, leaving the agent without decision-making support.

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