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

Annotations declare destructiveHint=true, readOnlyHint=false, so the mutation profile is known. The description adds real context beyond that: the one-rule-per-board free-plan limit, and it discloses that creating a rule has ongoing side effects. It does not mention permissions or that the rule executes asynchronously in the future, but it exceeds the annotation baseline.

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 capability, then the trigger taxonomy, then action taxonomy, then the plan limit. Every clause carries a required-field mapping or a constraint; no filler.

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 11-param tool with 0% schema coverage and no output schema, the description supplies the conditional-requirement graph that the schema lacks. It stops short of stating boardId/name semantics and creation preconditions, but no critical field mapping 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 0%, so the description carries the full burden and does so cleanly: it maps each trigger to its required id field and each action to its required companion field (actionListId, actionLabelId, actionUserId, actionDays, actionText). This is exactly the conditional parameter semantics the schema cannot express.

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 ('Adds a board rule') and fully enumerates the WHEN/THEN grammar available. An agent can distinguish this from delete_automation and set_automation_enabled 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?

It implies creation but never states when to use this versus alternatives, nor that a rule must be deleted rather than edited. The 'Free plan: 1 per board' constraint is the only boundary guidance, which is useful but incomplete.

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