create_dashboard

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

Since annotations are absent, the description fully conveys the key behavioral traits: it copies an existing dashboard, falls back to the first available if no source_block_id is given, and returns the new dashboard ID. No contradictions.

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?

The description is three sentences, front-loaded with the main purpose, and every sentence adds value. No redundant or vague phrases.

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?

With 3 parameters, no output schema, and no annotations, the description covers the tool's behavior, parameters, and return value adequately. It explains a crucial limitation (no scratch creation) which completes the context.

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?

Although schema description coverage is 100%, the description adds meaning by explaining the purpose of source_block_id (optional, fallback), and the necessity of app_token. It goes beyond schema by describing the copy mechanism.

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 clearly states 'Create a new dashboard in a Lark Base by copying an existing one,' specifying the verb (create), resource (dashboard), and method (copy). It distinguishes from sibling tools like create_chart_block, which create different entities.

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 description explains when to use (when a new dashboard is needed) and notes the API limitation (cannot create from scratch). It also clarifies behavior if source_block_id is omitted. However, it does not explicitly exclude scenarios or suggest alternatives like using list_dashboards first.

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