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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds a genuinely non-obvious behavioral fact — 'Saving a preset publishes nothing' — which guards against the reasonable misreading that fanning a post out across channels could trigger publishing. It does not discuss idempotency_key behavior despite the mutation.

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?

Two sentences, front-loaded with the action and resource, then the clarifying semantic. Every clause carries weight with no filler or restatement of the title.

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 an 8-parameter nested creation tool with no output schema, the description covers what is created and the key non-obvious behavior (no publishing). It stops short of noting the required idempotency key or workspace scoping, though those are partly documented in the schema itself.

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 description coverage is 75% and the schema documents name, channels, transform fields, defaults, and workspace_id reasonably well. The description clarifies the concept of 'channels with per-platform transformations' at a domain level but adds no field-level syntax or format guidance, so it hovers at the baseline for a well-covered schema.

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 ('Create a destination preset') and then defines what the resource actually is — a saved set of channels with per-platform transformations used for cross-channel fan-out. This is markedly more informative than the bare title and lets an agent distinguish it from siblings like aidelly_preview_destination_preset or aidelly_create_post.

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?

The fan-out sentence implies the purpose context, but there is no explicit when-to-use, when-not, or named alternative (e.g., preview vs. create vs. apply to a post). The agent must infer that this is the persistence step rather than the execution step.

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