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

No annotations are provided, so the description carries the full burden. It does disclose the shape of the returned data (a complete styling template covering font, color, animations, position), which is useful behavioral context, but says nothing about read-only safety, pagination, or any auth/permission requirements. Adequate but with clear gaps for an annotation-free tool.

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?

Three tight sentences, front-loaded with the purpose, then the payload description, then the actionable next step. No filler, no repetition of the tool name as a definition.

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 no output schema present, the description compensates by explaining what a preset contains and giving example categories, which is what an agent needs to decide whether to call it. It stops short of noting ordering, count, or stability of IDs, but for a static preset list this is close to 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?

The tool takes zero parameters, so per the baseline this scores 4. The description adds no parameter detail because none exists, and it correctly spends its words on return-value semantics instead.

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?

States a specific verb and resource ('Get the available text overlay presets') and immediately characterizes what a preset is, distinguishing it from sibling read tools. The description of preset contents (font, color, animations, position) and examples (cinematic titles, lower-thirds, subtitles, breaking news) make the resource concrete.

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?

Explicitly tells the agent how to act on the result: 'Use the preset ID with add_text_overlay to quickly create styled text,' which names the downstream sibling and the condition for using it. No exclusions or when-not guidance are given, but for a simple enumerating read tool the routing is clear.

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