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

Far beyond the annotations, the description discloses what actually gets written, the draft-vs-live state transition, that certain account-wide DM templates are refused, and that a connected Instagram account is required. This is exactly the mutation/authorization/rate behavior an agent needs and annotations alone would not provide.

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 two-mode behavior is front-loaded ('With no profile_id NOTHING is written'), and each subsequent sentence handles a distinct trigger case. It is dense but every sentence carries a rule; only slight tightening would help.

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 compensates by explaining that the check-only path hands the template back, and it covers the draft/live states and refusal case. For a nested-object, mutating tool, the coverage of behavior and prerequisites is 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?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine conditional meaning: it explains when post_id is required (single-post triggers) versus optional (keyword on any post, Profile DM), and clarifies profile_id as the write-enabling switch. It goes beyond restating the schema 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 states a specific verb (import/read) and resource (auto reply template), and lays out the two modes (check-only vs create). It does not name or contrast with the nearby siblings sprkly_create_automation_from_template or sprkly_export_automation_template, so the agent must infer the distinction, but the operation itself is 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?

It gives explicit conditional guidance: omitting profile_id is framed as 'the safe first call', and the post_id requirement is spelled out per trigger type. It stops short of naming alternative tools to reach for, but the when-to-use conditions are clear and actionable.

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