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

Annotations mark this as non-readOnly, non-destructive, non-idempotent, but the description goes further by disclosing the failure mode (nothing is created and `missing` is returned when a required field isn't detected) and the dry-run behavior, which the annotations do not convey.

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?

Dense and front-loaded: purpose first, then bindings, then failure mode, then dry_run. The long parenthetical template list and the trailing list_log_dashboards pointer are slightly bulky but each earns its place by preventing enumeration mistakes.

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 creation tool with no output schema and rich structured params, the definition covers purpose, override mechanism, precondition failure handling, preview, and the special-case parameter. Only the return shape on success is left implicit, which is a minor gap.

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 meaning: a concrete bindings example with syntax, the rule that null leaves an optional field empty, and the incident-war-room-only semantics of outage_uuid (window and service of that incident).

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?

The description opens with a specific verb+resource ('Creates a log dashboard from a ready-made template') and enumerates the template ids, so the agent can immediately tell this apart from read tools like list_log_dashboards or search_logs.

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 explains the key operational flow: fields are auto-detected, use `bindings` to override, retry with bindings when `missing` is returned, and `dry_run: true` previews. It also routes to list_log_dashboards for template scores. It lacks an explicit statement of when NOT to use it, but the context is clear.

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