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

Annotations only say readOnlyHint=false and non-destructive; the description goes far beyond by disclosing that omitting profile_id performs no write, that missing post_id produces an inert draft, and that whole-account DM templates are refused outright. These are exactly the side-effect and fallback behaviors an agent must know before calling.

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-loads the most important rule (no profile_id = nothing written) and every subsequent sentence encodes a distinct trigger/parameter branch, so the length is earned. It is a dense single paragraph, though, and could be marginally tightened.

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?

For a tool with a nested template object, three params, and no output schema, the description covers the write/no-write decision, the draft fallback, the required-parameter branches, and the refusal path, and even notes the template is handed back on a check call. Nothing essential to correct invocation is missing.

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 real conditional logic for post_id and profile_id (when each is required or optional, and the consequence of omitting them) that the flat schema fields do not fully convey. It stops short of template-object structure details.

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 pair (read/import an auto reply template, optionally setting it up) and disambiguates from the sibling sprkly_export_automation_template by naming the opposite direction. An agent immediately understands the dual check-vs-create nature without opening the schema.

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 prescribes the safe first call (no profile_id writes nothing), the condition that upgrades it to a write (profile_id), the extra requirement for single-post triggers (post_id), and the refusal case (whole-account DM templates). This is when/when-not guidance of the highest order, tied directly to parameter combinations.

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