ytptube_generate_history_nfo

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

The description does not add behavioral context beyond the annotations. Annotations indicate destructiveHint=true and readOnlyHint=false, but the description fails to explain what makes it destructive (e.g., overwriting existing NFO files) or any side effects. It adds no new safety information.

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 a single, front-loaded sentence that directly states the action and target. There is zero fluff or redundant information, making it extremely concise.

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?

With three parameters, annotations, and no output schema, the description is too sparse to be complete. It does not explain the return behavior, the meaning of 'NFO sidecar,' or how parameters affect the operation, leaving significant gaps for the agent.

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?

Schema description coverage is 0%, yet the description does not mention any parameters (id, type, overwrite). It fails to compensate for the schema's lack of descriptions, leaving the agent without guidance on how to populate these fields.

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's function: generating an NFO sidecar for a completed history item. The verb 'generate' is specific, and the resource 'NFO sidecar for a completed history item' distinguishes it from sibling tools like generate_task_metadata or get_history_item.

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 gives no guidance on when to use this tool versus alternatives. It only mentions 'completed history item,' which implies a prerequisite but does not explicitly state exclusions or provide context for choosing this over other history-related tools.

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