youtube_save_summary

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

No annotations are provided, so the description carries full burden. It mentions the output format but does not disclose behavioral traits like overwrite behavior, idempotency, authentication requirements, or error handling. This is insufficient for safe agent invocation.

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?

Single sentence of 8 words, front-loading the verb and resource. Every word is meaningful, no fluff. Perfectly 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?

Despite moderate complexity (7 params, no output schema), the description is very short. It lacks information on return values, success/failure indications, idempotency, and preconditions. An agent would need additional heuristics to use this safely.

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 high (86%), so baseline is 3. The description adds context that the summary is 'host-generated' and stored as Markdown with frontmatter, but does not elaborate on individual parameters beyond what the schema provides.

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 verb 'Persist' and the resource 'summary to the library', and specifies the format 'Markdown with frontmatter'. It distinguishes well from siblings 'youtube_get_transcript' and 'youtube_search', which are retrieval tools.

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 implies usage for saving a host-generated summary, and the sibling tools are obviously different. However, it lacks explicit guidance on when to use or not use this tool, such as prerequisites (e.g., summary must be generated by a host).

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