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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false, and the description adds real-world consequence detail ('starts replying to real people right away') plus a validation constraint (coupon template refused until message holds the real code). It does not say what happens on a duplicate call or what the tool returns, but the safety-relevant behavior is well covered.

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?

Front-loaded with the action and the user-visible warning, then the parameter rules; every sentence carries information. Slightly padded by the redundant restatement 'If it does not, leave post_id out,' which the preceding clause already implies.

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?

Covers setup, side effects, parameter conditions, a validation failure mode, and the off-switch, with no output schema to explain return values. The only gap is what an agent receives back (e.g., the created automation's id) for follow-up calls like pause/resume.

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 semantics beyond the schema: post_id only when asks_for has post and must be omitted otherwise, link must be a full https URL, keyword defaults to the template's word, and message replaces either the DM or the public reply on reply-only templates.

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+resource with scope ('Set up one ready-made automation on one Instagram account and turn it on') and maps it to a user-visible concept ('same as Go live in the app'). Clearly separable from siblings like sprkly_list_automation_templates, sprkly_import_automation_template, and sprkly_pause_automation.

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?

Gives explicit prerequisites (show the user the template, account, word and link first), names the source tools for template_id and profile_id, and routes to sprkly_pause_automation for stopping. Conditional rules for post_id and link are spelled out rather than left to inference.

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