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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the shape of each returned record (id, name, goal, trigger, message) and the availability note 'Every plan has automations', which preempts an empty-result question. It does not discuss ordering or pagination, but for a small read-only catalog that is a minor gap.

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 first sentence front-loads the identity of the tool and the gallery analogy, and the subsequent sentences each contribute something (examples, record fields, asks_for semantics, plan availability). It is slightly longer than a zero-parameter list tool strictly needs, but nothing is padding.

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, the description correctly compensates by enumerating the fields on each template and explaining the asks_for field that governs downstream creation. Combined with the availability note, an agent has enough to call it and interpret the result. Only the absence of ordering/size expectations keeps it from a 5.

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 the baseline is 4 and there is no parameter ambiguity to resolve. The description's discussion of asks_for describes the fields inside the response rather than input parameters, which is helpful but sits in the behavioral bucket rather than adding parameter meaning.

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 states a specific verb and resource: it lists ready-made Instagram automation templates, explicitly anchored to the in-app template gallery, which distinguishes it from sibling sprkly_list_automations (the user's own automations). It goes on to enumerate the use cases the templates cover (comment-to-link, story replies, follow-gate, email capture), so an agent knows exactly what this returns.

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?

Usage is clearly implied and partially explicit: the description names sprkly_create_automation_from_template and explains that asks_for tells you what that tool additionally requires, which effectively routes the agent from listing to creation. It stops short of a direct 'call this first, then call X' instruction and does not explicitly contrast with sprkly_list_automations, so it falls just below the full when/when-not bar.

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