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

Annotations already declare the non-destructive write profile (readOnlyHint=false, destructiveHint=false), and the description adds real behavior beyond that: availability gated on Dashly Plus with a hard cap of 3, and named failure modes PLAN_REQUIRED / DASHBOARD_LIMIT_REACHED. It also notes errors echo the offending path and allowed values. It stops short of other operational details (e.g. name collisions, ownership).

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?

Purpose is front-loaded and nearly every sentence carries actionable content, but it is a single dense paragraph with semicolon-heavy run-ons mixing document model, parameter semantics, and plan limits into one block. For a schema this complex some length is justified, though light structural separation 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?

An output schema exists, so return values need not be explained, and the description covers what remains: creation semantics, empty-start behavior, document structure, quota/plan failure modes, error reporting, and routing to siblings. Nothing an agent needs to invoke this correctly appears to be 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 nominally 100%, so the baseline is 3, but the description adds genuine semantics the schema does not: 'auto' size is derived from the widgets, density 'compact' packs tiles closer, and style overrides card color/icon with icon names drawn from tiles.icons. The widget-compatibility pointer to get_capabilities compensates for the many undescribed nested properties.

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?

Opens with a specific verb+resource ('Creates a dashboard besides home') and immediately scopes it against siblings: update_dashboard for adding cards later, get_capabilities for widget/size rules. An agent can tell this apart from create_topic, update_dashboard, and archive_dashboard without opening any 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?

Explicit when-to-use and when-to-go-elsewhere: empty start if no document, 'Add cards afterwards with update_dashboard', 'Which widgets each type allows... are in get_capabilities', and even design guidance ('Make one dashboard per theme... rather than one long wall'). Alternatives are named with the condition that selects them.

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